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

Swipick/swipick-backend

https://github.com/Swipick/swipick-backend · scanned 2026-06-16 00:27 UTC (2 months, 2 weeks ago)

175 raw signals (0 security + 175 graph)

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

Complete repo analysis

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

JSON
Combined
47.6
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 155 findings
Critical
4
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 4 High 8 Medium 10 Low 123 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 155 Crowd 0 Layer: Frontend 66 Network 1 Hardware 1 Security 5 Cicd 3 Quality 22 Api 57
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 47.6/100 with 100.0% coverage. It contains 1109 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 175 findings — concentrated in frontend (66), api (57), quality (22). Risk profile is high: 9 critical, 8 high, 13 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 145 of 155 actionable findings. 175 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 apps/frontend/frontend-service/contexts/RegistrationContext.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/frontend/frontend-service/contexts/RegistrationContext.tsx:88
critical System graph security Secrets conf 1.00 6 occurrences Possible secret in apps/frontend/frontend-service/types/auth.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 81, 82, 83, 92, 93, 98
apps/frontend/frontend-service/types/auth.ts:81, 82, 83, 92, 93, 98 (6 hits)
critical System graph security Secrets conf 1.00 Possible secret in backfill-giornata-5.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
backfill-giornata-5.ts:14
critical System graph security Secrets conf 1.00 Possible secret in fix-fixtures-from-giornata-23.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
fix-fixtures-from-giornata-23.ts:27
high System graph api Wiring conf 1.00 Dangling fetch: GET /fixtures/week/${weekNumber}${qs} (apps/frontend/frontend-service/lib/api-client.ts:135)
`apps/frontend/frontend-service/lib/api-client.ts:135` calls `GET /fixtures/week/${weekNumber}${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fixtures/week/<p>/<p>` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fixtures/week/${weekNumber}/daterange${qs} (apps/frontend/frontend-service/lib/api-client.ts:141)
`apps/frontend/frontend-service/lib/api-client.ts:141` calls `GET /fixtures/week/${weekNumber}/daterange${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fixtures/week/<p>/daterange/<p>` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /predictions/weekly/${userId}?mode=${mode} (apps/frontend/frontend-service/lib/api-client.ts:324)
`apps/frontend/frontend-service/lib/api-client.ts:324` calls `GET /predictions/weekly/${userId}?mode=${mode}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/predictions/weekly/<p>` If this points at an exte…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /test-mode/match-cards/week/${week}${qs} (apps/frontend/frontend-service/lib/api-client.ts:451)
`apps/frontend/frontend-service/lib/api-client.ts:451` calls `GET /test-mode/match-cards/week/${week}${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/test-mode/match-cards/week/<p>/<p>` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET https://swipick-backend-production-2650.up.railway.app/api/test-mode/fixtures/week/${week} (apps/frontend/frontend-service/app/gioca/utils/weekCalculator.ts:120)
`apps/frontend/frontend-service/app/gioca/utils/weekCalculator.ts:120` calls `GET https://swipick-backend-production-2650.up.railway.app/api/test-mode/fixtures/week/${week}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matchi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://v3.football.api-sports.io/fixtures (apps/backend/gaming-services/src/scripts/import-season-fixtures.ts:112)
`apps/backend/gaming-services/src/scripts/import-season-fixtures.ts:112` calls `GET https://v3.football.api-sports.io/fixtures` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/v3.football.api-sports.io/fixture…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://v3.football.api-sports.io/fixtures (apps/backend/gaming-services/src/scripts/resync-season-fixtures.ts:117)
`apps/backend/gaming-services/src/scripts/resync-season-fixtures.ts:117` calls `GET https://v3.football.api-sports.io/fixtures` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/v3.football.api-sports.io/fixture…
Dangling fetchAxios
high System graph cicd CI/CD security conf 1.00 GitHub Action tracks a moving branch
snyk/actions/node@master can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci-cd.yml:148 CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/frontend/frontend-service/lib/api-client.ts:292
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 — apps/frontend/frontend-service/public/swe-worker-5c72df51bb1f6ee0.js:1
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 — apps/frontend/frontend-service/public/workbox-9dfdb848.js:1
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 — scripts/test-user-predictions.js:18
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 cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
codecov/codecov-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 63, 226, 308, 317
.github/workflows/ci-cd.yml:63, 226, 308, 317 (4 hits)
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in apps/backend/gaming-services/src/modules/live-updates/live-updates.gateway.ts:16
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/backend/gaming-services/src/modules/live-updates/live-updates.gateway.ts:16 Cors wildcard
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 41 placeholder/mock markers across 16 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 network Security conf 1.00 Privileged port 1001 in use
Port 1001 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
apps/backend/bff/Dockerfile Ports
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 21 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CORS_ALLOWED_ORIGINS`, `CURRENT_SEASON`, `DISABLE_LIVE_UPDATES`, `FRONTEND_URL`, `MIGRATIONS_TS`, `NEON_DB_PORT`, `NEXT_PUBLIC_APP_URL`, `NEXT_PUBLIC_BFF_API_URL` + 13 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. 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 805 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 hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 3 locations
apps/backend/bff/Dockerfile:2, 27 (2 hits)
apps/backend/gaming-services/Dockerfile:2
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 11 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 21, 26, 77, 80, 120, 136, 139, 172, +3 more
.github/workflows/ci-cd.yml:21, 26, 77, 80, 120, 136, 139, 172, +3 more (11 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
34 tests / 229 src (ratio 0.15).
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/backend/bff/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/backend/bff/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/backend/gaming-services/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/backend/gaming-services/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/frontend/frontend-service/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/frontend/frontend-service/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/common/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/common/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `page_original_backup` in apps/frontend/frontend-service/eslint.config.mjs:16
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 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 — apps/backend/bff/src/run-migrations.ts:43
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 — apps/backend/gaming-services/populate-fixtures-2025.ts:8
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 — apps/backend/gaming-services/populate-fixtures-simple.ts:7
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 — apps/backend/gaming-services/populate-fixtures.ts:139
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 — apps/backend/gaming-services/repopulate-from-week-13.ts:9
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 — apps/backend/gaming-services/src/app.module.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 — apps/backend/gaming-services/src/database/migrations/1723456790000-CreateTestModeTablesFixturesAndSpecs.ts:167
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 — apps/backend/gaming-services/src/scripts/check-fixtures-integrity.ts:46
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 — apps/backend/gaming-services/src/scripts/import-season-fixtures.ts:85
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 — apps/backend/gaming-services/src/scripts/refresh-week-6-fixtures.ts:61
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 — apps/backend/gaming-services/src/scripts/refresh-week-7-fixtures.ts:61
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 — apps/backend/gaming-services/src/scripts/resync-season-fixtures.ts:99
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 — apps/backend/gaming-services/src/test-database.ts:8
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 — apps/backend/gaming-services/src/test-phase2-api.ts:10
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 — apps/backend/gaming-services/test-database.ts:8
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 — apps/frontend/frontend-service/app/gioca/components/GameHeader/GameHeader.tsx:79
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 — apps/frontend/frontend-service/app/gioca/components/GameHeader/TestGameHeader.tsx:148
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 — apps/frontend/frontend-service/app/gioca/components/MatchCard/LastFiveResults.tsx:21
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 — apps/frontend/frontend-service/app/gioca/components/TestGameSummaryScreen/TestGameSummaryScreen.tsx:105
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 — apps/frontend/frontend-service/app/gioca/hooks/useCountdown.ts:32
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 — apps/frontend/frontend-service/app/gioca/hooks/useFixtures.ts:57
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 — apps/frontend/frontend-service/app/gioca/hooks/useGameState.ts:127
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 — apps/frontend/frontend-service/app/gioca/hooks/useLiveWeek.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 — apps/frontend/frontend-service/app/gioca/hooks/usePredictions.ts:114
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 — apps/frontend/frontend-service/app/gioca/page.tsx:48
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 — apps/frontend/frontend-service/app/gioca/testGioca/page.tsx:42
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 — apps/frontend/frontend-service/app/gioca/utils/weekCalculator.ts:33
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 — apps/frontend/frontend-service/app/login/page.tsx:22
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 — apps/frontend/frontend-service/app/profilo/page.tsx:170
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 — apps/frontend/frontend-service/app/profilo/testProfilo/page.tsx:33
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 — apps/frontend/frontend-service/app/registro/page.tsx:57
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 — apps/frontend/frontend-service/app/risultati/page.tsx:311
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 — apps/frontend/frontend-service/app/risultati/test-risultati/page.tsx:198
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 — apps/frontend/frontend-service/contexts/RegistrationContext.tsx:205
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 — apps/frontend/frontend-service/create-icons.js:13
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 — apps/frontend/frontend-service/lib/api-client.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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/frontend/frontend-service/next.config.ts:4
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 — apps/frontend/frontend-service/services/googleAuth.ts:13
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 — apps/frontend/frontend-service/src/components/auth/EmailVerificationPrompt.tsx:31
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 — apps/frontend/frontend-service/src/components/auth/LoginForm.tsx:38
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 — apps/frontend/frontend-service/src/contexts/AuthContext.tsx:117
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 — apps/frontend/frontend-service/src/contexts/LoginContext.tsx:140
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 — apps/frontend/frontend-service/src/hooks/useLogin.tsx:25
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 — backfill-giornata-5.ts:39
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 — fix-fixtures-from-giornata-23.ts:54
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 — populate-fixtures.js:161
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 — scripts/add-week6-specs-user2.js:14
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 — scripts/add-week6-specs-user3.js:14
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 — scripts/add-week6-specs.js:14
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 — scripts/check-specs-weeks.js:11
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 — scripts/check-user-specs.js:11
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 — scripts/check-week6-specs.js:13
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 — scripts/check-week7-users.js:11
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 — scripts/fix-spec-weeks.js:11
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 — scripts/test-spec-week-fix.js:11
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 — scripts/test-user-predictions.js:7
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 — scripts/verify-week6-results.js:13
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 — seed-test-fixtures.js:72
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/predictions/user/:userId
`apps/backend/bff/src/app.controller.ts` declares `DELETE /api/predictions/user/:userId` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/test-mode/reset/:userId
`apps/backend/bff/src/app.controller.ts` declares `DELETE /api/test-mode/reset/:userId` 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: DELETE /final-week-scores/:userId/week/:week
`apps/backend/gaming-services/src/modules/final-week-scores/final-week-scores.controller.ts` declares `DELETE /final-week-scores/:userId/week/:week` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherw…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/polling/efficiency
`apps/backend/gaming-services/src/modules/live-updates/polling-stats.controller.ts` declares `GET /admin/polling/efficiency` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/polling/health
`apps/backend/gaming-services/src/modules/live-updates/polling-stats.controller.ts` declares `GET /admin/polling/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 — conside…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/polling/stats
`apps/backend/gaming-services/src/modules/live-updates/polling-stats.controller.ts` declares `GET /admin/polling/stats` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/fixtures/:id
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/: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/fixtures/last-played
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/last-played` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/fixtures/live
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/live` 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/fixtures/next
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/next` 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/fixtures/upcoming/serie-a
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/upcoming/serie-a` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/fixtures/week/:weekNumber
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/week/:weekNumber` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/fixtures/week/:weekNumber/daterange
`apps/backend/bff/src/app.controller.ts` declares `GET /api/fixtures/week/:weekNumber/daterange` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`apps/backend/bff/src/app.controller.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 /api/match-cards/week/:weekNumber
`apps/backend/bff/src/app.controller.ts` declares `GET /api/match-cards/week/:weekNumber` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/teams/:id
`apps/backend/bff/src/app.controller.ts` declares `GET /api/teams/: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/teams/:id/statistics
`apps/backend/bff/src/app.controller.ts` declares `GET /api/teams/:id/statistics` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/teams/:id1/vs/:id2
`apps/backend/bff/src/app.controller.ts` declares `GET /api/teams/:id1/vs/:id2` 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/test-mode/fixtures/week/:week
`apps/backend/bff/src/app.controller.ts` declares `GET /api/test-mode/fixtures/week/:week` 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/test-mode/progression/:userId
`apps/backend/bff/src/app.controller.ts` declares `GET /api/test-mode/progression/:userId` 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 /final-week-scores/:userId/statistics
`apps/backend/gaming-services/src/modules/final-week-scores/final-week-scores.controller.ts` declares `GET /final-week-scores/:userId/statistics` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /final-week-scores/:userId/week/:week/percentile
`apps/backend/gaming-services/src/modules/final-week-scores/final-week-scores.controller.ts` declares `GET /final-week-scores/:userId/week/:week/percentile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks)…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fixtures/next
`apps/backend/gaming-services/src/modules/fixtures/fixtures.controller.ts` declares `GET /fixtures/next` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fixtures/quota/status
`apps/backend/gaming-services/src/modules/fixtures/fixtures.controller.ts` declares `GET /fixtures/quota/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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fixtures/week/:weekNumber
`apps/backend/gaming-services/src/modules/fixtures/fixtures.controller.ts` declares `GET /fixtures/week/:weekNumber` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fixtures/week/:weekNumber/daterange
`apps/backend/gaming-services/src/modules/fixtures/fixtures.controller.ts` declares `GET /fixtures/week/:weekNumber/daterange` 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 — c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/api-status
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/api-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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/daily-fixtures
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/daily-fixtures` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/find-serie-a-season
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/find-serie-a-season` 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 de…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/leagues
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/leagues` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/live-matches
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/live-matches` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/test-connection
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/test-connection` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/debug/test-raw-api
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/debug/test-raw-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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live-updates/polling-stats
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `GET /live-updates/polling-stats` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /match-cards/week/:weekNumber
`apps/backend/gaming-services/src/modules/match-cards/match-cards.controller.ts` declares `GET /match-cards/week/:weekNumber` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /test-mode/debug-api-call
`apps/backend/gaming-services/src/modules/test-mode/test-mode.controller.ts` declares `GET /test-mode/debug-api-call` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /test-mode/health
`apps/backend/gaming-services/src/modules/test-mode/test-mode.controller.ts` declares `GET /test-mode/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /test-mode/match-cards/week/:week
`apps/backend/gaming-services/src/modules/test-mode/test-mode.controller.ts` declares `GET /test-mode/match-cards/week/:week` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /test-mode/predictions/user/:userId/summary
`apps/backend/gaming-services/src/modules/test-mode/test-mode.controller.ts` declares `GET /test-mode/predictions/user/:userId/summary` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /test-mode/predictions/user/:userId/week/:week
`apps/backend/gaming-services/src/modules/test-mode/test-mode.controller.ts` declares `GET /test-mode/predictions/user/:userId/week/:week` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/polling/check/:fixtureId
`apps/backend/gaming-services/src/modules/live-updates/polling-stats.controller.ts` declares `POST /admin/polling/check/:fixtureId` 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 cod…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/fixtures/sync
`apps/backend/bff/src/app.controller.ts` declares `POST /api/fixtures/sync` 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/fixtures/sync/season
`apps/backend/bff/src/app.controller.ts` declares `POST /api/fixtures/sync/season` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/test-mode/progression/:userId/next
`apps/backend/bff/src/app.controller.ts` declares `POST /api/test-mode/progression/:userId/next` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fixtures/quota/clear-cache
`apps/backend/gaming-services/src/modules/fixtures/fixtures.controller.ts` declares `POST /fixtures/quota/clear-cache` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fixtures/sync/season
`apps/backend/gaming-services/src/modules/fixtures/fixtures.controller.ts` declares `POST /fixtures/sync/season` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /live-updates/backfill-results/:date
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `POST /live-updates/backfill-results/:date` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /live-updates/manual-check-all
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `POST /live-updates/manual-check-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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /live-updates/manual-check/:fixtureId
`apps/backend/gaming-services/src/modules/live-updates/live-updates.controller.ts` declares `POST /live-updates/manual-check/:fixtureId` 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 dea…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /test-mode/seed-full-season
`apps/backend/gaming-services/src/modules/test-mode/test-mode.controller.ts` declares `POST /test-mode/seed-full-season` 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 — conside…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/frontend-service/app/risultati/page.tsx (1195 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/frontend-service/app/risultati/test-risultati/page.tsx (1403 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/95cb75e1-b3ae-4448-a58a-953b757e052f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/95cb75e1-b3ae-4448-a58a-953b757e052f/

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.