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

ShanuX69420/GAMESBAZAARV6

https://github.com/ShanuX69420/GAMESBAZAARV6 · scanned 2026-06-16 00:09 UTC (2 months, 2 weeks ago)

117 raw signals (0 security + 117 graph)

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

Complete repo analysis

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

JSON
Combined
71.9
/100
Security checks
72
0 findings
System graph
72
100.0% cov · 104 findings
Critical
1
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 1 High 1 Medium 29 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 104 Crowd 0 Layer: Software 2 Frontend 1 Security 9 Cicd 1 Quality 41 Api 50
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 71.9/100 with 100.0% coverage. It contains 2269 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 117 findings — concentrated in quality (54), api (50), security (9). Risk profile is high: 1 critical, 1 high, 29 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 101 of 104 actionable findings. 117 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 System graph security Secrets conf 1.00 Possible secret in backend/seed_data.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/seed_data.py:40
high System graph security auth conf 1.00 DRF view `ListingDetailView` declares no `permission_classes` — backend/core/views.py:1874
DRF defaults to AllowAny when `permission_classes` is unset, exposing the endpoint publicly. Add `permission_classes = [IsAuthenticated]` (or stricter) at class level, or set `DEFAULT_PERMISSION_CLASSES` in settings.
backend/core/views.py:1874 securityAuth drf no permission classes
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/components/JsonLd.js:12
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 — frontend/app/games/[slug]/[categorySlug]/GameCategoryClient.js:158
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 — frontend/app/games/[slug]/[categorySlug]/layout.js:11
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 — frontend/app/games/[slug]/[categorySlug]/page.js:20
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 — frontend/app/sitemap.js:20
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 — frontend/lib/api.js:41
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 — frontend/lib/auth.js:34
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 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 auth conf 1.00 Django CBV `RefreshTokenView` lacks `LoginRequiredMixin` — backend/core/views.py:964
Class-based view defines mutating methods (post/put/delete) without inheriting `LoginRequiredMixin`. If auth is enforced via `dispatch()` override or middleware, dismiss this finding.
backend/core/views.py:964 Auth django unauth view
medium System graph security auth conf 1.00 Django view `game_list_cache_key` may be unauthenticated — backend/core/views.py:153
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
backend/core/views.py:153 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `get_before_id` may be unauthenticated — backend/core/views.py:315
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
backend/core/views.py:315 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `get_pagination_params` may be unauthenticated — backend/core/views.py:288
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
backend/core/views.py:288 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `has_valid_private_media_ticket` may be unauthenticated — backend/core/views.py:192
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
backend/core/views.py:192 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `request_origin_cache_scope` may be unauthenticated — backend/core/views.py:149
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
backend/core/views.py:149 securityAuth django unauth view
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/components/JsonLd.js:12
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/components/JsonLd.js:12 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for gc in …` triggers a query per row — backend/core/management/commands/export_catalog.py:32
The loop iterates a Django queryset and accesses `gc.game.name` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries instead…
backend/core/management/commands/export_catalog.py:32 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for gc in …` triggers a query per row — backend/core/views.py:4160
The loop iterates a Django queryset and accesses `gc.game.icon` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries instead…
backend/core/views.py:4160 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for gcf in …` triggers a query per row — backend/core/management/commands/copy_category_filters.py:46
The loop iterates a Django queryset and accesses `gcf.visible_when_options.all` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2…
backend/core/management/commands/copy_category_filters.py:46 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for gcf in …` triggers a query per row — backend/core/management/commands/copy_category_filters.py:74
The loop iterates a Django queryset and accesses `gcf.visible_when_options.all` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2…
backend/core/management/commands/copy_category_filters.py:74 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for gcf in …` triggers a query per row — backend/core/migrations/0052_gamecategoryfilter_visible_when_options_m2m.py:13
The loop iterates a Django queryset and accesses `gcf.visible_when_options.order_by` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything i…
backend/core/migrations/0052_gamecategoryfilter_visible_when_options_m2m.py:13 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for gcf in …` triggers a query per row — backend/core/migrations/0052_gamecategoryfilter_visible_when_options_m2m.py:7
The loop iterates a Django queryset and accesses `gcf.visible_when_options.add` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2…
backend/core/migrations/0052_gamecategoryfilter_visible_when_options_m2m.py:7 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for order in …` triggers a query per row — backend/core/views.py:2646
The loop iterates a Django queryset and accesses `order.buyer.username` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries…
backend/core/views.py:2646 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for sibling in …` triggers a query per row — backend/core/models.py:199
The loop iterates a Django queryset and accesses `sibling.category.slug` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 querie…
backend/core/models.py:199 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for target in …` triggers a query per row — backend/core/management/commands/copy_category_filters.py:68
The loop iterates a Django queryset and accesses `target.assigned_filters.all` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 …
backend/core/management/commands/copy_category_filters.py:68 N plus onePerformance
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — deploy/backup_db.py:27
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
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 71 placeholder/mock markers across 24 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
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 30 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 Tests conf 1.00 Low test-to-source ratio
19 tests / 185 src (ratio 0.10).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 12 places
Functions with the same first-5-line body hash: backend/core/serializers.py:validate_accepted_terms, backend/core/serializers.py:validate, backend/core/serializers.py:validate, backend/core/serializers.py:validate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see h…
duplicatesduplication
low System graph quality Integrity conf 1.00 13 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/core/serializers.py:get_listing_count, backend/core/serializers.py:get_listing_count This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separa…
13 occurrences
repo-level (13 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/core/views.py:delete, backend/core/views.py:delete, backend/core/views.py:delete This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 30 places
Functions with the same first-5-line body hash: backend/core/views.py:get_throttles, backend/core/views.py:get, backend/core/views.py:get, backend/core/views.py:get This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or doc…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 38 places
Functions with the same first-5-line body hash: backend/core/views.py:post, backend/core/views.py:post, backend/core/views.py:post, backend/core/views.py:post This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/core/views.py:put, backend/core/views.py:put, backend/core/views.py:put, backend/core/views.py:put This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: backend/core/admin.py:save_model, backend/core/admin.py:save_model, backend/core/admin.py:save_model, backend/core/admin.py:save_model This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). …
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 `list_objects_v2` in deploy/backup_db.py:46
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: option_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/seed_data.py:605
low System graph software Dead code conf 1.00 Possibly dead Python function: refund_mwallet_payment
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/core/jazzcash.py:212
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 api Wiring conf 1.00 Unused endpoint: ANY /^media/(?P<path>.*)$
`backend/gamesbazaar/urls.py` declares `ANY /^media/(?P<path>.*)$` 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: ANY /admin/
`backend/gamesbazaar/urls.py` declares `ANY /admin/` 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: ANY /api/
`backend/gamesbazaar/urls.py` declares `ANY /api/` 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: ANY /api/auth/avatar/
`backend/core/urls.py` declares `ANY /api/auth/avatar/` 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: ANY /api/auth/complete-profile/
`backend/core/urls.py` declares `ANY /api/auth/complete-profile/` 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: ANY /api/auth/email/confirm-change/
`backend/core/urls.py` declares `ANY /api/auth/email/confirm-change/` 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: ANY /api/auth/email/request-change/
`backend/core/urls.py` declares `ANY /api/auth/email/request-change/` 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: ANY /api/auth/google/
`backend/core/urls.py` declares `ANY /api/auth/google/` 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: ANY /api/auth/login/
`backend/core/urls.py` declares `ANY /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: ANY /api/auth/logout/
`backend/core/urls.py` declares `ANY /api/auth/logout/` 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: ANY /api/auth/me/
`backend/core/urls.py` declares `ANY /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: ANY /api/auth/password/
`backend/core/urls.py` declares `ANY /api/auth/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: ANY /api/auth/password/reset-confirm/
`backend/core/urls.py` declares `ANY /api/auth/password/reset-confirm/` 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: ANY /api/auth/password/reset-request/
`backend/core/urls.py` declares `ANY /api/auth/password/reset-request/` 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: ANY /api/auth/profile/
`backend/core/urls.py` declares `ANY /api/auth/profile/` 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: ANY /api/auth/refresh/
`backend/core/urls.py` declares `ANY /api/auth/refresh/` 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: ANY /api/auth/register/
`backend/core/urls.py` declares `ANY /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: ANY /api/auth/resend-verification/
`backend/core/urls.py` declares `ANY /api/auth/resend-verification/` 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: ANY /api/auth/verify-email/
`backend/core/urls.py` declares `ANY /api/auth/verify-email/` 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: ANY /api/chat/
`backend/core/urls.py` declares `ANY /api/chat/` 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: ANY /api/chat/<int:pk>/
`backend/core/urls.py` declares `ANY /api/chat/<int:pk>/` 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: ANY /api/chat/<int:pk>/send-image/
`backend/core/urls.py` declares `ANY /api/chat/<int:pk>/send-image/` 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: ANY /api/chat/<int:pk>/send/
`backend/core/urls.py` declares `ANY /api/chat/<int:pk>/send/` 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: ANY /api/chat/<int:pk>/ws-ticket/
`backend/core/urls.py` declares `ANY /api/chat/<int:pk>/ws-ticket/` 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: ANY /api/chat/inbox/ws-ticket/
`backend/core/urls.py` declares `ANY /api/chat/inbox/ws-ticket/` 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: ANY /api/chat/messages/<int:pk>/image/
`backend/core/urls.py` declares `ANY /api/chat/messages/<int:pk>/image/` 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: ANY /api/chat/start/
`backend/core/urls.py` declares `ANY /api/chat/start/` 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: ANY /api/chat/unread/
`backend/core/urls.py` declares `ANY /api/chat/unread/` 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: ANY /api/games/
`backend/core/urls.py` declares `ANY /api/games/` 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: ANY /api/games/<slug:game_slug>/<slug:category_slug>/
`backend/core/urls.py` declares `ANY /api/games/<slug:game_slug>/<slug:category_slug>/` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/games/<slug:slug>/
`backend/core/urls.py` declares `ANY /api/games/<slug:slug>/` 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: ANY /api/heartbeat/
`backend/core/urls.py` declares `ANY /api/heartbeat/` 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: ANY /api/home/popular/
`backend/core/urls.py` declares `ANY /api/home/popular/` 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: ANY /api/listings/
`backend/core/urls.py` declares `ANY /api/listings/` 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: ANY /api/listings/<int:pk>/
`backend/core/urls.py` declares `ANY /api/listings/<int:pk>/` 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: ANY /api/listings/<int:pk>/restock/
`backend/core/urls.py` declares `ANY /api/listings/<int:pk>/restock/` 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: ANY /api/listings/<int:pk>/stock/
`backend/core/urls.py` declares `ANY /api/listings/<int:pk>/stock/` 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: ANY /api/listings/mine/
`backend/core/urls.py` declares `ANY /api/listings/mine/` 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: ANY /api/payments/jazzcash/buy/
`backend/core/urls.py` declares `ANY /api/payments/jazzcash/buy/` 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: ANY /api/payments/jazzcash/top-up/
`backend/core/urls.py` declares `ANY /api/payments/jazzcash/top-up/` 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: ANY /api/seller/apply/
`backend/core/urls.py` declares `ANY /api/seller/apply/` 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: ANY /api/seller/dashboard/
`backend/core/urls.py` declares `ANY /api/seller/dashboard/` 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: ANY /api/seller/status/
`backend/core/urls.py` declares `ANY /api/seller/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: ANY /api/wallet/
`backend/core/urls.py` declares `ANY /api/wallet/` 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: ANY /api/wallet/held-orders/
`backend/core/urls.py` declares `ANY /api/wallet/held-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: ANY /api/wallet/top-up/
`backend/core/urls.py` declares `ANY /api/wallet/top-up/` 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: ANY /api/wallet/top-up/<int:pk>/proof/
`backend/core/urls.py` declares `ANY /api/wallet/top-up/<int:pk>/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: ANY /api/wallet/transactions/
`backend/core/urls.py` declares `ANY /api/wallet/transactions/` 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: ANY /api/wallet/withdraw/
`backend/core/urls.py` declares `ANY /api/wallet/withdraw/` 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: ANY /api/wallet/withdraw/<int:pk>/receipt/
`backend/core/urls.py` declares `ANY /api/wallet/withdraw/<int:pk>/receipt/` 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: backend/core/models.py (1325 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/core/serializers.py (1668 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/core/services.py (1594 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/core/tests.py (9942 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/core/views.py (4599 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/games/[slug]/[categorySlug]/GameCategoryClient.js (1280 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/24d77372-a87e-4fd7-b5ee-98cd39959d77/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/24d77372-a87e-4fd7-b5ee-98cd39959d77/

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.