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

said019/kala-Studio

https://github.com/said019/kala-Studio · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

144 raw signals (4 security + 140 graph)

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

Complete repo analysis

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

JSON
Combined
64.0
/100
Security checks
64
3 findings
System graph
64
88.9% cov · 127 findings
Critical
2
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 2 High 21 Medium 14 Low 64 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 127 Crowd 0 Layer: Quality 23 Security 7 Software 1 Frontend 27 Cicd 1 Api 71
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 64.0/100 with 88.9% coverage. It contains 1749 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 140 findings — concentrated in api (71), quality (34), frontend (27). Risk profile is high: 1 critical, 21 high, 25 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 101 of 130 actionable findings. 146 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: said019/kala-Studio
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in server/index.js:5436
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
server/index.js:5436 Private key in repo
high System graph api Wiring conf 1.00 Dangling fetch: GET https://walletobjects.googleapis.com/walletobjects/v1/loyaltyClass/${GW_CLASS_ID} (server/index.js:5506)
`server/index.js:5506` calls `GET https://walletobjects.googleapis.com/walletobjects/v1/loyaltyClass/${GW_CLASS_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/walletobjects.googleapis.com/walletobjects/v…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/drive/v3/files/${fileId}?alt=media (server/index.js:13689)
`server/index.js:13689` calls `GET https://www.googleapis.com/drive/v3/files/${fileId}?alt=media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>` If this points at an ext…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/drive/v3/files/${fileId}?alt=media (server/index.js:13755)
`server/index.js:13755` calls `GET https://www.googleapis.com/drive/v3/files/${fileId}?alt=media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>` If this points at an ext…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/drive/v3/files/${fileId}?fields=mimeType,name (server/index.js:13750)
`server/index.js:13750` calls `GET https://www.googleapis.com/drive/v3/files/${fileId}?fields=mimeType,name` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>` If this point…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/drive/v3/files/${fileId}?fields=mimeType,size,name (server/index.js:13661)
`server/index.js:13661` calls `GET https://www.googleapis.com/drive/v3/files/${fileId}?fields=mimeType,size,name` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>` If this …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (server/index.js:13415)
`server/index.js:13415` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (server/index.js:16110)
`server/index.js:16110` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (server/index.js:422)
`server/index.js:422` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefix it with `https://` …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (server/index.js:5473)
`server/index.js:5473` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefix it with `https://`…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://walletobjects.googleapis.com/walletobjects/v1/loyaltyClass (server/index.js:5517)
`server/index.js:5517` calls `POST https://walletobjects.googleapis.com/walletobjects/v1/loyaltyClass` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/walletobjects.googleapis.com/walletobjects/v1/loyaltyclass…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://walletobjects.googleapis.com/walletobjects/v1/loyaltyObject (server/index.js:6583)
`server/index.js:6583` calls `POST https://walletobjects.googleapis.com/walletobjects/v1/loyaltyObject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/walletobjects.googleapis.com/walletobjects/v1/loyaltyobje…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/drive/v3/files/${fileId}/permissions (server/index.js:432)
`server/index.js:432` calls `POST https://www.googleapis.com/drive/v3/files/${fileId}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>/permissions` If this poi…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/drive/v3/files/${uploadJson.id}/permissions (server/index.js:13448)
`server/index.js:13448` calls `POST https://www.googleapis.com/drive/v3/files/${uploadJson.id}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>/permissions` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/drive/v3/files/${uploadJson.id}/permissions (server/index.js:16141)
`server/index.js:16141` calls `POST https://www.googleapis.com/drive/v3/files/${uploadJson.id}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/drive/v3/files/<p>/permissions` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id (server/index.js:13439)
`server/index.js:13439` calls `POST https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/upload/drive/v3/files` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id (server/index.js:16133)
`server/index.js:16133` calls `POST https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/upload/drive/v3/files` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id,webViewLink (server/index.js:471)
`server/index.js:471` calls `POST https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id,webViewLink` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/upload/drive/v3…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/upload/drive/v3/files?uploadType=resumable&fields=id,webViewLink (server/index.js:13513)
`server/index.js:13513` calls `POST https://www.googleapis.com/upload/drive/v3/files?uploadType=resumable&fields=id,webViewLink` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/upload/drive/…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/upload/drive/v3/files?uploadType=resumable&fields=id,webViewLink (server/index.js:494)
`server/index.js:494` calls `POST https://www.googleapis.com/upload/drive/v3/files?uploadType=resumable&fields=id,webViewLink` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.googleapis.com/upload/drive/v3…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://walletobjects.googleapis.com/walletobjects/v1/loyaltyClass/${GW_CLASS_ID} (server/index.js:5510)
`server/index.js:5510` calls `PUT https://walletobjects.googleapis.com/walletobjects/v1/loyaltyClass/${GW_CLASS_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/walletobjects.googleapis.com/walletobjects/v…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://walletobjects.googleapis.com/walletobjects/v1/loyaltyObject/${objectIdPath} (server/index.js:6575)
`server/index.js:6575` calls `PUT https://walletobjects.googleapis.com/walletobjects/v1/loyaltyObject/${objectIdPath}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/walletobjects.googleapis.com/walletobjects…
Dangling fetchAxios
medium Security checks quality Practices conf 0.62 3 occurrences Foundry mined assumption checks: said019/kala-Studio
Comment chain pattern product: assumption_checks Repo: said019/kala-Studio Thread: said019/kala-Studio#3 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_gr…
3 occurrences
repo-level (3 hits)
medium Security checks quality maintenance conf 0.70 2 occurrences Foundry mined blueprint gap alignment: said019/kala-Studio
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
2 occurrences
repo-level (2 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/ui/chart.tsx:70
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/index.js:13415
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 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 quality Integrity conf 1.00 14 occurrences Frontend route `/auth/reset-password` has no Link/navigate to it — src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
14 occurrences
repo-level (14 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in endpoint-auditor/scripts/audit_runner.py:232
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
endpoint-auditor/scripts/audit_runner.py:232 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in endpoint-auditor/SKILL.md:113
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
endpoint-auditor/SKILL.md:113 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/ui/chart.tsx:70
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/ui/chart.tsx:70 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/stores/authStore.ts:80
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/stores/authStore.ts:80 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/index.js:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/index.js:17 Node child process
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 186 placeholder/mock markers across 50 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
12 test file(s) for 167 source file(s) (ratio 0.07). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 61 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADDON_ONLINE_PRICE`, `ADMIN_ID`, `APPLE_APNS_HOST`, `APPLE_APNS_KEY`, `APPLE_APNS_KEY_BASE64`, `APPLE_APNS_KEY_PATH`, `APPLE_APNS_KEY_PEM`, `APPLE_AUTH_TOKEN` + 53 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't b…
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 112 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 quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: tools/generate_wallet_visual_assets.py:render_wallet_icon, tools/generate_wallet_visual_assets.py:render_wallet_thumb This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or do…
duplicatesduplication
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 Integrity conf 1.00 Old/deprecated-named symbol `admin_phones_seed_v1` in server/index.js:1715
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `kala_video_upload_v1` in src/pages/admin/videos/VideoUpload.tsx:63
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: replacer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
endpoint-auditor/scripts/audit_runner.py:80
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/emailService.js:173
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/index.js:768
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: DELETE /api/bookings/:id
`server/index.js` declares `DELETE /api/bookings/:id` 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: DELETE /api/wallet/v1/devices/:deviceId/registrations/:passTypeId/:serial
`server/index.js` declares `DELETE /api/wallet/v1/devices/:deviceId/registrations/:passTypeId/:serial` 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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/notifications
`server/index.js` declares `GET /api/admin/notifications` 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/admin/notifications/unread-count
`server/index.js` declares `GET /api/admin/notifications/unread-count` 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/admin/rings/users/:id
`server/index.js` declares `GET /api/admin/rings/users/:id` 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/admin/wallet/notifications
`server/index.js` declares `GET /api/admin/wallet/notifications` 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/auth/me
`server/index.js` declares `GET /api/auth/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: GET /api/bookings/my-bookings
`server/index.js` declares `GET /api/bookings/my-bookings` 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/bookings/weekly-status
`server/index.js` declares `GET /api/bookings/weekly-status` 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/classes
`server/index.js` declares `GET /api/classes` 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/classes/:id
`server/index.js` declares `GET /api/classes/:id` 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/loyalty/my-history
`server/index.js` declares `GET /api/loyalty/my-history` 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/loyalty/rewards
`server/index.js` declares `GET /api/loyalty/rewards` 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/me/notifications
`server/index.js` declares `GET /api/me/notifications` 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/me/notifications/unread-count
`server/index.js` declares `GET /api/me/notifications/unread-count` 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/me/rings
`server/index.js` declares `GET /api/me/rings` 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/me/video-access
`server/index.js` declares `GET /api/me/video-access` 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/memberships/mine/all
`server/index.js` declares `GET /api/memberships/mine/all` 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/memberships/my
`server/index.js` declares `GET /api/memberships/my` 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/orders
`server/index.js` declares `GET /api/orders` 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/orders/:id
`server/index.js` declares `GET /api/orders/:id` 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/plans
`server/index.js` declares `GET /api/plans` 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/wallet/apple/debug
`server/index.js` declares `GET /api/wallet/apple/debug` 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/wallet/apple/pkpass
`server/index.js` declares `GET /api/wallet/apple/pkpass` 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/wallet/apple/status
`server/index.js` declares `GET /api/wallet/apple/status` 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/wallet/events/apple/pkpass
`server/index.js` declares `GET /api/wallet/events/apple/pkpass` 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/wallet/events/google/save-url
`server/index.js` declares `GET /api/wallet/events/google/save-url` 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/wallet/google/diagnostics
`server/index.js` declares `GET /api/wallet/google/diagnostics` 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/wallet/google/save-url
`server/index.js` declares `GET /api/wallet/google/save-url` 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/wallet/pass
`server/index.js` declares `GET /api/wallet/pass` 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/wallet/v1/devices/:deviceId/registrations/:passTypeId
`server/index.js` declares `GET /api/wallet/v1/devices/:deviceId/registrations/:passTypeId` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/wallet/v1/passes/:passTypeId/:serial
`server/index.js` declares `GET /api/wallet/v1/passes/:passTypeId/:serial` 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 /api/admin/memberships/:id/grant-weekly-extra
`server/index.js` declares `POST /api/admin/memberships/:id/grant-weekly-extra` 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 /api/admin/notifications/mark-read
`server/index.js` declares `POST /api/admin/notifications/mark-read` 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 /api/admin/rings/community-events
`server/index.js` declares `POST /api/admin/rings/community-events` 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 /api/auth/change-password
`server/index.js` declares `POST /api/auth/change-password` 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 /api/auth/forgot-password
`server/index.js` declares `POST /api/auth/forgot-password` 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 /api/auth/login
`server/index.js` declares `POST /api/auth/login` 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 /api/auth/onboarding
`server/index.js` declares `POST /api/auth/onboarding` 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 /api/auth/register
`server/index.js` declares `POST /api/auth/register` 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 /api/auth/reset-password
`server/index.js` declares `POST /api/auth/reset-password` 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 /api/bookings
`server/index.js` declares `POST /api/bookings` 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 /api/discount-codes/validate
`server/index.js` declares `POST /api/discount-codes/validate` 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 /api/loyalty/redeem
`server/index.js` declares `POST /api/loyalty/redeem` 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 /api/me/notifications/mark-read
`server/index.js` declares `POST /api/me/notifications/mark-read` 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 /api/orders
`server/index.js` declares `POST /api/orders` 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 /api/orders/:id/proof
`server/index.js` declares `POST /api/orders/:id/proof` 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 /api/reviews
`server/index.js` declares `POST /api/reviews` 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 /api/wallet/v1/devices/:deviceId/registrations/:passTypeId/:serial
`server/index.js` declares `POST /api/wallet/v1/devices/:deviceId/registrations/:passTypeId/:serial` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/wallet/v1/log
`server/index.js` declares `POST /api/wallet/v1/log` 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/index.js (17595 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/admin/classes/ClassesCalendar.tsx (1805 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/Index.tsx (2039 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/e8c1931b-e0ac-41ab-b00f-fc4a6a0bedd7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e8c1931b-e0ac-41ab-b00f-fc4a6a0bedd7/

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.