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

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)

File as issue Image
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
Combined
53.9
/100
Security checks
54
0 findings
System graph
54
100.0% cov · 102 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 12 Medium 26 Low 44 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 102 Crowd 0 Layer: Frontend 15 Security 12 Cicd 1 Quality 38 Api 36
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 53.9/100 with 100.0% coverage. It contains 511 nodes across 24 cross-layer flows, written primarily in mixed languages. Engine surfaced 102 findings — concentrated in quality (38), api (36), frontend (15). Risk profile is high: 0 critical, 12 high, 26 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 81 of 102 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/balance?customer_key=${encodeURIComponent(customerKey)} (src/services/api.ts:131)
`src/services/api.ts:131` calls `GET /api/balance?customer_key=${encodeURIComponent(customerKey)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/balance` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/order/check?order_id=${encodeURIComponent(orderId)} (src/services/api.ts:100)
`src/services/api.ts:100` calls `GET /api/order/check?order_id=${encodeURIComponent(orderId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/order/check` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/order/find-recent?customer_key=${encodeURIComponent(customerKey)} (src/services/api.ts:121)
`src/services/api.ts:121` calls `GET /api/order/find-recent?customer_key=${encodeURIComponent(customerKey)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/order/find-recent` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.yookassa.ru/v3/payments/${existingPending.payment_id} (supabase/functions/create-payment/index.ts:114)
`supabase/functions/create-payment/index.ts:114` calls `GET https://api.yookassa.ru/v3/payments/${existingPending.payment_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.yookassa.ru/v3/payments/<p>` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.yookassa.ru/v3/payments/${order.payment_id} (supabase/functions/check-order/index.ts:108)
`supabase/functions/check-order/index.ts:108` calls `GET https://api.yookassa.ru/v3/payments/${order.payment_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.yookassa.ru/v3/payments/<p>` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/generation/pair (src/services/api.ts:213)
`src/services/api.ts:213` calls `POST /api/generation/pair` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/generation/pair` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/generation/single (src/services/api.ts:187)
`src/services/api.ts:187` calls `POST /api/generation/single` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/generation/single` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/payment/create (src/services/api.ts:77)
`src/services/api.ts:77` calls `POST /api/payment/create` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/payment/create` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST https://ai.gateway.lovable.dev/v1/chat/completions (supabase/functions/create-payment/index.ts:180)
`supabase/functions/create-payment/index.ts:180` calls `POST https://ai.gateway.lovable.dev/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/ai.gateway.lovable.dev/v1/chat/completions` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://ai.gateway.lovable.dev/v1/chat/completions (supabase/functions/retry-generation/index.ts:41)
`supabase/functions/retry-generation/index.ts:41` calls `POST https://ai.gateway.lovable.dev/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/ai.gateway.lovable.dev/v1/chat/completions` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.yookassa.ru/v3/payments (supabase/functions/create-payment/index.ts:325)
`supabase/functions/create-payment/index.ts:325` calls `POST https://api.yookassa.ru/v3/payments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.yookassa.ru/v3/payments` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.yookassa.ru/v3/refunds (supabase/functions/auto-refund-order/index.ts:220)
`supabase/functions/auto-refund-order/index.ts:220` calls `POST https://api.yookassa.ru/v3/refunds` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.yookassa.ru/v3/refunds` If this points at an external API…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/services/openrouter.ts:120
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/services/replicate.ts:82
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/services/yookassa.ts:86
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/screens/ResultsScreen.tsx:53
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/auto-refund-order/index.ts:220
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/check-order/index.ts:123
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/cleanup-orders/index.ts:72
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/create-payment/index.ts:114
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/auto-refund-order/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/auto-refund-order/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/check-order/index.ts:6
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/check-order/index.ts:6 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/cleanup-orders/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/cleanup-orders/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/create-payment/index.ts:6
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/create-payment/index.ts:6 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/find-recent-order/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/find-recent-order/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/generate-one/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/generate-one/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/generate-photo/index.ts:6
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/generate-photo/index.ts:6 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/get-balance/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/get-balance/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/pay-with-credits/index.ts:21
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/pay-with-credits/index.ts:21 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/retry-generation/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/retry-generation/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/yookassa-webhook/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/yookassa-webhook/index.ts:5 Cors wildcard
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 12 placeholder/mock markers across 5 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 62 source file(s) (ratio 0.03). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 11 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CLUB_DISCOUNT_PERCENT`, `DAILY_GENERATION_LIMIT`, `DIAGNOSTIC_TOKEN`, `FREE_ARCHIVE_TTL_MINUTES`, `PHOTO_TEMP_DIR`, `PHOTO_TTL_MINUTES`, `REPLICATE_ADAPTER`, `REPLICATE_API_TOKEN` + 3 more. Add them (with a placeholder/comment) to .env.example so …
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 135 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/components/ProfileOverlay.tsx:39
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/index.ts:107
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/routes/generation.ts:207
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/routes/payment.ts:130
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/components/screens/ResultsScreen.tsx:261
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/auto-refund-order/index.ts:63
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/check-order/index.ts:66
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/cleanup-orders/index.ts:44
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/create-payment/index.ts:120
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/generate-one/index.ts:71
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/generate-photo/index.ts:172
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/retry-generation/index.ts:162
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/validate-code/index.ts:74
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/yookassa-webhook/index.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`server/routes/balance.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:filename
`server/routes/photos.ts` declares `GET /:filename` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/config
`server/index.ts` declares `GET /api/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`server/index.ts` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /check
`server/routes/order.ts` declares `GET /check` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /diagnostic
`server/routes/payment.ts` declares `GET /diagnostic` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /download/:filename
`server/routes/photos.ts` declares `GET /download/:filename` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /find-recent
`server/routes/order.ts` declares `GET /find-recent` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /me
`server/routes/referrals.ts` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /create
`server/routes/payment.ts` declares `POST /create` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /debit
`server/routes/credits.ts` declares `POST /debit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /pair
`server/routes/generation.ts` declares `POST /pair` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /single
`server/routes/generation.ts` declares `POST /single` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /track
`server/routes/referrals.ts` declares `POST /track` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /upload
`server/routes/photos.ts` declares `POST /upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/balance
`server/index.ts` declares `USE /api/balance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/credits
`server/index.ts` declares `USE /api/credits` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/generation
`server/index.ts` declares `USE /api/generation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/order
`server/index.ts` declares `USE /api/order` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/payment
`server/index.ts` declares `USE /api/payment` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/payment/create
`server/index.ts` declares `USE /api/payment/create` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/photos
`server/index.ts` declares `USE /api/photos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/referrals
`server/index.ts` declares `USE /api/referrals` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/styles
`server/index.ts` declares `USE /api/styles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: server/services/prompts.ts (1879 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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.