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

tpals0409/AlgoSu

https://github.com/tpals0409/AlgoSu · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

182 raw signals (0 security + 182 graph)

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

Complete repo analysis

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

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

Showing 109 of 147 actionable findings. 182 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 4 occurrences Possible secret in infra/postgres-init/01-create-databases.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 17, 18, 19, 20
infra/postgres-init/01-create-databases.sh:17, 18, 19, 20 (4 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/commands/algosu-review.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/commands/algosu-review.md:24 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:99 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.github.com/repos/${owner}/${repo}/installation (services/github-worker/src/token-manager.ts:75)
`services/github-worker/src/token-manager.ts:75` calls `POST https://api.github.com/repos/${owner}/${repo}/installation` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>/installatio…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `check_and_increment_quota` without auth dependency — services/ai-analysis/src/main.py:269
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ai-analysis/src/main.py:269 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `group_analysis` without auth dependency — services/ai-analysis/src/main.py:328
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ai-analysis/src/main.py:328 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — blog/src/app/en/layout.tsx:26
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/ui/chart.tsx:85
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/src/contexts/AuthContext.tsx:175
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/src/hooks/__tests__/useSubmissionSSE.test.ts:47
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/src/lib/guards.ts:17
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/src/lib/quiz/__tests__/api-store.test.ts:65
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 — services/gateway/src/share/public-share.controller.ts:98
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 — services/gateway/src/study/study-stats.service.ts:72
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/agents/_base.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/agents/_base.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/agents/critic.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/agents/critic.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/algosu-oracle.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/algosu-oracle.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/stop.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/stop.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. 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 hardware Security conf 1.00 Dockerfile runs as root: blog/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
github/codeql-action/upload-sarif@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:1091 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/dependabot-automerge.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/ci.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in blog/src/app/en/layout.tsx:26
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
blog/src/app/en/layout.tsx:26 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/ui/chart.tsx:85
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/ui/chart.tsx:85 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in blog/src/components/blog/mermaid.tsx:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
blog/src/components/blog/mermaid.tsx:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-coverage-gate-bypass.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-coverage-gate-bypass.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-doc-refs.mjs:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-doc-refs.mjs:34 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-prometheus-rules.mjs:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-prometheus-rules.mjs:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-staging-integrity.mjs:45
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-staging-integrity.mjs:45 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 88 placeholder/mock markers across 36 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 18 in use
Port 18 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/ci-full-validation.yml Ports
low System graph quality Integrity conf 1.00 18 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANALYZE`, `DATABASE_POOL_MAX`, `DATABASE_POOL_MIN`, `DATABASE_SSL`, `ENV`, `GITHUB_OUTPUT`, `GITHUB_STEP_SUMMARY`, `MONITORING_SRC` + 10 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 100 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 Docker base image is tag-pinned but not digest-pinned: nginx:1.28-alpine3.21
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
blog/Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 12 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
6 files, 12 locations
frontend/Dockerfile:3, 24 (2 hits)
services/gateway/Dockerfile:4, 36 (2 hits)
services/github-worker/Dockerfile:2, 9 (2 hits)
services/identity/Dockerfile:3, 11 (2 hits)
services/problem/Dockerfile:3, 11 (2 hits)
services/submission/Dockerfile:4, 12 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.13-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 11
services/ai-analysis/Dockerfile:2, 11 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 21 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/github-script@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 21 locations
.github/workflows/ci.yml:324, 442, 591, 610, 627, 648, 664, 694, +11 more (19 hits)
.github/workflows/ci-full-validation.yml:41
.github/workflows/dependabot-automerge.yml:35
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
184 tests / 892 src (ratio 0.21).
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 `deleteOld` in services/identity/src/notification/notification.controller.spec.ts:41
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deleteOld` in services/identity/src/notification/notification.controller.ts:97
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deleteOld` in services/identity/src/notification/notification.service.spec.ts:188
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deleteOld` in services/identity/src/notification/notification.service.ts:120
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `missing_in_old` in services/problem/src/database/reconciliation.service.ts:85
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
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 — frontend/scripts/check-wcag.ts:207
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/components/providers/WebVitalsReporter.tsx:26
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 — frontend/src/hooks/__tests__/useAutoSave.test.ts: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 — scripts/verify-routes.ts: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 — services/gateway/src/share/public-share.controller.spec.ts:187
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 — tests/e2e/programmers-full-flow.spec.ts:333
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 /:id
`services/problem/src/problem/problem.controller.ts` declares `DELETE /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/notifications/by-user/:userId
`services/identity/src/notification/notification.controller.ts` declares `DELETE /api/notifications/by-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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/notifications/old
`services/identity/src/notification/notification.controller.ts` declares `DELETE /api/notifications/old` 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: DELETE /api/studies/:id
`services/identity/src/study/study.controller.ts` declares `DELETE /api/studies/: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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/studies/:id/members/:userId
`services/identity/src/study/study.controller.ts` declares `DELETE /api/studies/:id/members/: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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/users/:id
`services/identity/src/user/user.controller.ts` declares `DELETE /api/users/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:id
`services/problem/src/problem/problem.controller.ts` declares `GET /: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 /active
`services/problem/src/problem/problem.controller.ts` declares `GET /active` 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 /all
`services/problem/src/problem/problem.controller.ts` declares `GET /all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/feedbacks/:publicId/detail
`services/identity/src/feedback/feedback.controller.ts` declares `GET /api/feedbacks/:publicId/detail` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/feedbacks/by-user/:userId
`services/identity/src/feedback/feedback.controller.ts` declares `GET /api/feedbacks/by-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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/invites/by-code/:code
`services/identity/src/study/study.controller.ts` declares `GET /api/invites/by-code/:code` 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/notifications/by-user/:userId
`services/identity/src/notification/notification.controller.ts` declares `GET /api/notifications/by-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 remov…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/notifications/by-user/:userId/unread-count
`services/identity/src/notification/notification.controller.ts` declares `GET /api/notifications/by-user/:userId/unread-count` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/quiz-records/by-user/:userId
`services/identity/src/quiz-record/quiz-record.controller.ts` declares `GET /api/quiz-records/by-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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/share-links/by-token/:token
`services/identity/src/share/share-link.controller.ts` declares `GET /api/share-links/by-token/:token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/share-links/by-user/:userId/study/:studyId
`services/identity/src/share/share-link.controller.ts` declares `GET /api/share-links/by-user/:userId/study/:studyId` 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 /api/studies/:id
`services/identity/src/study/study.controller.ts` declares `GET /api/studies/: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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/studies/:id/members
`services/identity/src/study/study.controller.ts` declares `GET /api/studies/:id/members` 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/studies/:id/members/:userId
`services/identity/src/study/study.controller.ts` declares `GET /api/studies/:id/members/: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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/studies/by-user/:userId
`services/identity/src/study/study.controller.ts` declares `GET /api/studies/by-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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/users/:id
`services/identity/src/user/user.controller.ts` declares `GET /api/users/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/users/:id/github-encrypted-token
`services/identity/src/user/user.controller.ts` declares `GET /api/users/:id/github-encrypted-token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/users/:id/github-status
`services/identity/src/user/user.controller.ts` declares `GET /api/users/:id/github-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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/users/:id/github-token
`services/identity/src/user/user.controller.ts` declares `GET /api/users/:id/github-token` 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/users/by-slug/:slug
`services/identity/src/user/user.controller.ts` declares `GET /api/users/by-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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /circuit-breaker/status
`services/ai-analysis/src/main.py` declares `GET /circuit-breaker/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /internal/:id
`services/problem/src/problem/internal-problem.controller.ts` declares `GET /internal/: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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /internal/active-ids/:studyId
`services/problem/src/problem/internal-problem.controller.ts` declares `GET /internal/active-ids/:studyId` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /internal/deadline/:id
`services/problem/src/problem/internal-problem.controller.ts` declares `GET /internal/deadline/: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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /quota
`services/ai-analysis/src/main.py` declares `GET /quota` 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 /search/tags
`services/problem/src/problem/problem.controller.ts` declares `GET /search/tags` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /week/:weekNumber
`services/problem/src/problem/problem.controller.ts` declares `GET /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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id
`services/problem/src/problem/problem.controller.ts` declares `PATCH /: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: PATCH /api/invites/:id/consume
`services/identity/src/study/study.controller.ts` declares `PATCH /api/invites/:id/consume` 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: PATCH /api/notifications/:id/read
`services/identity/src/notification/notification.controller.ts` declares `PATCH /api/notifications/:id/read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/notifications/by-user/:userId/read-all
`services/identity/src/notification/notification.controller.ts` declares `PATCH /api/notifications/by-user/:userId/read-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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/share-links/:id/deactivate
`services/identity/src/share/share-link.controller.ts` declares `PATCH /api/share-links/:id/deactivate` 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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/studies/:id/members/:userId/nickname
`services/identity/src/study/study.controller.ts` declares `PATCH /api/studies/:id/members/:userId/nickname` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/studies/:id/members/:userId/role
`services/identity/src/study/study.controller.ts` declares `PATCH /api/studies/:id/members/:userId/role` 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: PATCH /api/users/:id
`services/identity/src/user/user.controller.ts` declares `PATCH /api/users/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/users/:id/github
`services/identity/src/user/user.controller.ts` declares `PATCH /api/users/:id/github` 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: PATCH /api/users/:id/profile-settings
`services/identity/src/user/user.controller.ts` declares `PATCH /api/users/:id/profile-settings` 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 /api/studies
`services/identity/src/study/study.controller.ts` declares `POST /api/studies` 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/studies/:id/invites
`services/identity/src/study/study.controller.ts` declares `POST /api/studies/:id/invites` 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: POST /api/studies/:id/members
`services/identity/src/study/study.controller.ts` declares `POST /api/studies/:id/members` 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: POST /api/users/upsert
`services/identity/src/user/user.controller.ts` declares `POST /api/users/upsert` 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 /group-analysis
`services/ai-analysis/src/main.py` declares `POST /group-analysis` 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 /quota/check
`services/ai-analysis/src/main.py` declares `POST /quota/check` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/studies/:id
`services/identity/src/study/study.controller.ts` declares `PUT /api/studies/: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 …
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: scripts/check-grafana-metrics.mjs (1352 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/ai-analysis/tests/test_claude_client.py (1804 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/ai-analysis/tests/test_worker.py (1388 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/submission/src/submission/submission.service.spec.ts (1324 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/66e98294-9317-4f25-a7ca-acb1ed9f3951/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/66e98294-9317-4f25-a7ca-acb1ed9f3951/

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.