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

tannpv/draftright

https://github.com/tannpv/draftright · scanned 2026-06-16 00:30 UTC (2 months, 2 weeks ago)

169 raw signals (0 security + 169 graph)

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

Complete repo analysis

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

JSON
Combined
44.3
/100
Security checks
44
0 findings
System graph
44
100.0% cov · 141 findings
Critical
3
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 3 High 5 Medium 27 Low 85 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 141 Crowd 0 Layer: Software 11 Frontend 11 Hardware 7 Security 9 Cicd 3 Quality 46 Api 54
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 44.3/100 with 100.0% coverage. It contains 2276 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 169 findings — concentrated in quality (58), api (54), cicd (16). Risk profile is high: 4 critical, 5 high, 30 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 117 of 141 actionable findings. 169 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.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.lemonsqueezy.com/v1/customers/${user.lemonsqueezy_customer_id} (backend/src/payment/strategies/lemonsqueezy.strategy.ts:161)
`backend/src/payment/strategies/lemonsqueezy.strategy.ts:161` calls `DELETE https://api.lemonsqueezy.com/v1/customers/${user.lemonsqueezy_customer_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.lemon…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://appleid.apple.com/auth/keys (backend/src/auth/auth.service.ts:464)
`backend/src/auth/auth.service.ts:464` calls `GET https://appleid.apple.com/auth/keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/appleid.apple.com/auth/keys` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://graph.facebook.com/me?fields=id,name,email,picture.type(large)&access_token=${accessToken} (backend/src/auth/auth.service.ts:485)
`backend/src/auth/auth.service.ts:485` calls `GET https://graph.facebook.com/me?fields=id,name,email,picture.type(large)&access_token=${accessToken}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.faceb…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://oauth2.googleapis.com/tokeninfo?id_token=${idToken} (backend/src/auth/auth.service.ts:368)
`backend/src/auth/auth.service.ts:368` calls `GET https://oauth2.googleapis.com/tokeninfo?id_token=${idToken}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/tokeninfo` If this points at…
Dangling fetchFetch
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: admin/.env.production
`admin/.env.production` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
admin/.env.production ConfigEnv fileRuntime env
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — admin/src/api.ts:8
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 — admin/src/pages/BugReportsPage.tsx:90
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 — backend/src/ai-providers/strategies/anthropic.strategy.ts:38
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 — backend/src/ai-providers/strategies/openai.strategy.ts:48
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 — backend/src/auth/auth.service.ts:368
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 — backend/src/lemonsqueezy/lemonsqueezy.service.ts:58
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 — backend/src/payment/strategies/lemonsqueezy.strategy.ts:127
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 — website/src/components/AccountPage.tsx:117
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 — website/src/components/FeedbackBoard.tsx:227
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 — website/src/components/Playground.tsx:83
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 — website/src/components/SuggestFeatureWidget.tsx:53
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. 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: admin/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `/users/:id` has no Link/navigate to it — admin/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/build-windows.yml:186, 386 (2 hits)
DraftRightMobile/.github/workflows/play-deploy.yml:35, 41 (2 hits)
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/build-windows.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in admin/src/auth.ts:22
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
admin/src/auth.ts:22 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in website/src/components/Checkout.tsx:186
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
website/src/components/Checkout.tsx:186 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in website/src/components/LoginForm.tsx:30
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
website/src/components/LoginForm.tsx:30 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in website/src/components/SignupForm.tsx:35
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
website/src/components/SignupForm.tsx:35 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in website/src/lib/socialAuth.ts:87
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
website/src/lib/socialAuth.ts:87 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — DraftRightLinux/draftright/ui/settings_window.py:461
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 139 placeholder/mock markers across 48 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality 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 20 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BACKEND_URL`, `DISPLAY`, `DRAFTRIGHT_BACKEND_URL`, `GDK_BACKEND`, `GO_BACKEND_RAMP_PERCENT`, `LANG`, `NODE_ENV`, `OTEL_EXPORTER_OTLP_ENDPOINT` + 12 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 92 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: gcr.io/distroless/static-debian12:nonroot
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend-rewrite-go/Dockerfile:36 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.25-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend-rewrite-go/Dockerfile:5 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
admin/Dockerfile:30 containersPinned dependencies
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
backend/Dockerfile:1, 9 (2 hits)
admin/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@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 11 locations
.github/workflows/build-windows.yml:55, 58, 113, 178, 213, 216, 378, 381, +1 more (9 hits)
DraftRightMobile/.github/workflows/play-deploy.yml:26, 29 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — admin/src/components/Toast.tsx:62
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: DraftRightLinux/draftright/services/settings_service.py:backend_url, DraftRightLinux/draftright/services/settings_service.py:backend_url This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene)…
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/seed-keyboard-multi-ios-test-cases.py:main, scripts/seed-single-instance-test-cases.py:main, scripts/seed-keyboard-multi-test-cases.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-co…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: DraftRightLinux/draftright/services/payment_service.py:kind, DraftRightLinux/draftright/services/payment_service.py:kind, DraftRightLinux/draftright/services/payment_service.py:kind, DraftRightLinux/draftright/services/payment_service.py:kind This is…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_on_copy` in DraftRightLinux/draftright/ui/checkout_dialogs.py:184
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 `_simulate_copy` in DraftRightLinux/draftright/services/clipboard_service.py:69
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 `on_copy` in DraftRightLinux/draftright/ui/rewrite_panel.py:257
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: do_activate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/application.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: do_download
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/application.py:349
low System graph software Dead code conf 1.00 Possibly dead Python function: is_x11
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/helpers/display_server.py:11
low System graph software Dead code conf 1.00 Possibly dead Python function: load
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/services/settings_service.py:156
low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/services/auth_service.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: report_handled
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/services/error_reporter.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: set_auto_start
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/services/settings_service.py:184
low System graph software Dead code conf 1.00 Possibly dead Python function: show_with_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/ui/rewrite_panel.py:272
low System graph software Dead code conf 1.00 Possibly dead Python function: worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/ui/suggest_feature_dialog.py:154
low System graph software Dead code conf 1.00 Possibly dead Python function: worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DraftRightLinux/draftright/ui/subscription_page.py:237
low System graph software Dead code conf 1.00 Possibly dead Python function: wrap_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/gen-screenshots.py:76
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — admin/src/pages/BugReportsPage.tsx:58
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
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 — admin/e2e/report-bug.spec.ts:55
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 — backend/scripts/generate-openapi.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 — backend/scripts/sync-stripe-prices.js: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 — backend/scripts/sync-stripe-prices.ts:62
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 — backend/src/main.ts:59
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 — backend/src/seed.ts:29
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 /admin/bug-reports/:id
`backend/src/admin/admin.controller.ts` declares `DELETE /admin/bug-reports/: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: DELETE /admin/email-templates/:key
`backend/src/admin/admin.controller.ts` declares `DELETE /admin/email-templates/:key` 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: DELETE /admin/errors/:id
`backend/src/admin/admin.controller.ts` declares `DELETE /admin/errors/: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 /admin/releases/:platform/:channel
`backend/src/admin/admin.controller.ts` declares `DELETE /admin/releases/:platform/:channel` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /auth/account
`backend/src/auth/auth.controller.ts` declares `DELETE /auth/account` 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 /auth/extension-tokens/:id
`backend/src/auth/extension-token.controller.ts` declares `DELETE /auth/extension-tokens/: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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/bug-reports
`backend/src/admin/admin.controller.ts` declares `GET /admin/bug-reports` 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 /admin/bug-reports/:id
`backend/src/admin/admin.controller.ts` declares `GET /admin/bug-reports/: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 /admin/bug-reports/:id/screenshot
`backend/src/admin/admin.controller.ts` declares `GET /admin/bug-reports/:id/screenshot` 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: GET /admin/email-logs
`backend/src/admin/admin.controller.ts` declares `GET /admin/email-logs` 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 /admin/email-templates
`backend/src/admin/admin.controller.ts` declares `GET /admin/email-templates` 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 /admin/email-templates/:key/preview
`backend/src/admin/admin.controller.ts` declares `GET /admin/email-templates/:key/preview` 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 /admin/errors
`backend/src/admin/admin.controller.ts` declares `GET /admin/errors` 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 /admin/errors/:id
`backend/src/admin/admin.controller.ts` declares `GET /admin/errors/: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 /admin/inbox
`backend/src/admin/admin.controller.ts` declares `GET /admin/inbox` 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 /admin/inbox/counts
`backend/src/admin/admin.controller.ts` declares `GET /admin/inbox/counts` 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 /admin/plans
`backend/src/admin/admin.controller.ts` declares `GET /admin/plans` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/releases
`backend/src/admin/admin.controller.ts` declares `GET /admin/releases` 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 /admin/settings
`backend/src/admin/admin.controller.ts` declares `GET /admin/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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/stats
`backend/src/admin/admin.controller.ts` declares `GET /admin/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 removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/users
`backend/src/admin/admin.controller.ts` declares `GET /admin/users` 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 /admin/users/:id
`backend/src/admin/admin.controller.ts` declares `GET /admin/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 /auth/account
`backend/src/auth/auth.controller.ts` declares `GET /auth/account` 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 /auth/me
`backend/src/auth/auth.controller.ts` declares `GET /auth/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ime-packs/manifest
`backend/src/ime-packs/ime-packs.controller.ts` declares `GET /ime-packs/manifest` 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 /lemonsqueezy/portal
`backend/src/lemonsqueezy/lemonsqueezy.controller.ts` declares `GET /lemonsqueezy/portal` 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 /updates/latest
`backend/src/updates/updates.controller.ts` declares `GET /updates/latest` 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 /admin/bug-reports/:id
`backend/src/admin/admin.controller.ts` declares `PATCH /admin/bug-reports/: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 /admin/email-templates/:key
`backend/src/admin/admin.controller.ts` declares `PATCH /admin/email-templates/:key` 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: PATCH /admin/errors/:id
`backend/src/admin/admin.controller.ts` declares `PATCH /admin/errors/: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 /admin/settings
`backend/src/admin/admin.controller.ts` declares `PATCH /admin/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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /admin/users/:id
`backend/src/admin/admin.controller.ts` declares `PATCH /admin/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: POST /admin/bug-reports/:id/fix-proposal
`backend/src/admin/admin.controller.ts` declares `POST /admin/bug-reports/:id/fix-proposal` 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 /admin/errors/:id/suggest-fix
`backend/src/admin/admin.controller.ts` declares `POST /admin/errors/:id/suggest-fix` 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: POST /admin/errors/run-ai-cron
`backend/src/admin/admin.controller.ts` declares `POST /admin/errors/run-ai-cron` 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 /admin/plans
`backend/src/admin/admin.controller.ts` declares `POST /admin/plans` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/release-policies
`backend/src/admin/admin.controller.ts` declares `POST /admin/release-policies` 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 /admin/releases
`backend/src/admin/admin.controller.ts` declares `POST /admin/releases` 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 /admin/settings/test-email
`backend/src/admin/admin.controller.ts` declares `POST /admin/settings/test-email` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/change-password
`backend/src/auth/auth.controller.ts` declares `POST /auth/change-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/forgot-password
`backend/src/auth/auth.controller.ts` declares `POST /auth/forgot-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/login
`backend/src/auth/auth.controller.ts` declares `POST /auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/refresh
`backend/src/auth/auth.controller.ts` declares `POST /auth/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/register
`backend/src/auth/auth.controller.ts` declares `POST /auth/register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/resend-verification
`backend/src/auth/auth.controller.ts` declares `POST /auth/resend-verification` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/reset-password
`backend/src/auth/auth.controller.ts` declares `POST /auth/reset-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/social
`backend/src/auth/auth.controller.ts` declares `POST /auth/social` 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 /auth/verify-email
`backend/src/auth/auth.controller.ts` declares `POST /auth/verify-email` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /lemonsqueezy/checkout
`backend/src/lemonsqueezy/lemonsqueezy.controller.ts` declares `POST /lemonsqueezy/checkout` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /lemonsqueezy/webhook
`backend/src/lemonsqueezy/lemonsqueezy.controller.ts` declares `POST /lemonsqueezy/webhook` 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
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/f51f6f22-fa06-420d-9f06-0d3b91bee55d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f51f6f22-fa06-420d-9f06-0d3b91bee55d/

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.