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.

ramxak2025/zr-auto-pro

https://github.com/ramxak2025/zr-auto-pro · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

238 raw signals (15 security + 223 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 213 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 6 Medium 18 Low 87 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 213 Crowd 0 Layer: Quality 122 Security 6 Frontend 31 Network 1 Hardware 8 Cicd 1 Api 52

Exclude dismissed / FP Exclude test files

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 65.5/100 with 100.0% coverage. It contains 3272 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 223 findings — concentrated in quality (123), api (52), frontend (31). Risk profile is high: 0 critical, 2 high, 23 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical Security checks security auth conf 0.78 2 occurrences Foundry mined security auth guardrail gaps: ramxak2025/zr-auto-pro

Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…

2 occurrences

repo-level (2 hits)

high Security checks quality Practices conf 0.84 3 occurrences Foundry mined bad chains: ramxak2025/zr-auto-pro

Comment chain pattern product: bad_chains Repo: ramxak2025/zr-auto-pro Thread: ramxak2025/zr-auto-pro#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, sourc…

3 occurrences

repo-level (3 hits)

high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: ramxak2025/zr-auto-pro

Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: supported_by_ve…

high Security checks quality Quality conf 0.76 3 occurrences Foundry mined schema ui api mismatch: ramxak2025/zr-auto-pro

Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: weak_supervision_needs_review Repo: r…

3 occurrences

repo-level (3 hits)

high Security checks quality Testing conf 0.78 Foundry mined test ci gap after feedback: ramxak2025/zr-auto-pro

Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: assumption_check Repo: …

high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (frontend/src/hooks/useRoutePrefetch.ts:36)

`frontend/src/hooks/useRoutePrefetch.ts:36` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://sms.ru/sms/send?${params.toString()} (backend/src/marketing/marketing.service.ts:53)

`backend/src/marketing/marketing.service.ts:53` calls `GET https://sms.ru/sms/send?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/sms.ru/sms/send` If this points at an external API, pref…

Dangling fetchFetch

medium Security checks quality Practices conf 0.62 4 occurrences Foundry mined assumption checks: ramxak2025/zr-auto-pro

Comment chain pattern product: assumption_checks Repo: ramxak2025/zr-auto-pro Thread: ramxak2025/zr-auto-pro#7 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, sou…

4 occurrences

repo-level (4 hits)

medium Security checks quality maintenance conf 0.70 5 occurrences Foundry mined blueprint gap alignment: ramxak2025/zr-auto-pro

Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …

5 occurrences

repo-level (5 hits)

medium Security checks quality Practices conf 0.70 9 occurrences Foundry mined unresolved feedback: ramxak2025/zr-auto-pro

Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: assu…

9 occurrences

repo-level (9 hits)

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/src/marketing/marketing.service.ts: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 security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/ios-qa-build/SKILL.md

Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.

.claude/skills/ios-qa-build/SKILL.md:57 Supply chainClaude 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: 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 hardware Security conf 1.00 Dockerfile runs as root: frontend/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: webhook/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 9 occurrences Frontend route `/review/:token` has no Link/navigate to it — frontend/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.

9 occurrences

repo-level (9 hits)

Orphan pageWiring

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/hooks/usePullToRefresh.ts:44

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

frontend/src/hooks/usePullToRefresh.ts:44 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/utils/generateReceiptPdf.ts:57

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

frontend/src/utils/generateReceiptPdf.ts:57 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/contexts/AuthContext.tsx:159

Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.

frontend/src/contexts/AuthContext.tsx:159 Local storage auth token

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/pages/admin/AdminTenantDetailPage.tsx:220

Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.

frontend/src/pages/admin/AdminTenantDetailPage.tsx:220 Local storage auth token

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 367 placeholder/mock markers across 87 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 254 in use

Port 254 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

scripts/full-setup.sh Ports

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

7 test file(s) for 412 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.

Coverage

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/pages/KnowledgeBasePage.tsx:346

A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…

Fq active light bg

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/pages/SchedulePage.tsx:768

Fq active light bg

low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `APP_URL`, `DATABASE_URL`, `DB_HOST`, `DB_NAME`, `DB_PORT`, `DB_USER`, `NODE_ENV`, `PORT` + 1 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.19

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

webhook/Dockerfile:6 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.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.

webhook/Dockerfile:1 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.

frontend/Dockerfile:11 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, 7 (2 hits)

frontend/Dockerfile:1

containersPinned dependencies

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 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 api Wiring conf 1.00 Unused endpoint: DELETE /employees/:id/achievements/:achId

`backend/src/employees/employees.controller.ts` declares `DELETE /employees/:id/achievements/:achId` 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 /employees/:id/documents/:docId

`backend/src/employees/employees.controller.ts` declares `DELETE /employees/:id/documents/:docId` 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: DELETE /push/token

`shared/api/createServices.ts` declares `DELETE /push/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 consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /schedule/:id

`backend/src/schedule/schedule.controller.ts` declares `DELETE /schedule/: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 /users/:id

`backend/src/users/users.controller.ts` declares `DELETE /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 /clients/export-csv

`shared/api/createServices.ts` declares `GET /clients/export-csv` 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 /employees/:id/achievements

`backend/src/employees/employees.controller.ts` declares `GET /employees/:id/achievements` 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 /employees/:id/documents

`backend/src/employees/employees.controller.ts` declares `GET /employees/:id/documents` 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 /employees/:id/documents/:docId/file

`backend/src/employees/employees.controller.ts` declares `GET /employees/:id/documents/:docId/file` 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 /employees/:id/full-profile

`backend/src/employees/employees.controller.ts` declares `GET /employees/:id/full-profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/broadcasts/unseen

`backend/src/notifications/notifications.controller.ts` declares `GET /notifications/broadcasts/unseen` 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: GET /notifications/preferences

`backend/src/notifications/notifications.controller.ts` declares `GET /notifications/preferences` 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 /products/export-csv

`shared/api/createServices.ts` declares `GET /products/export-csv` 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 /schedule/my-stats

`backend/src/schedule/schedule.controller.ts` declares `GET /schedule/my-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 /schedule/settings

`backend/src/schedule/schedule.controller.ts` declares `GET /schedule/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 /schedule/today

`backend/src/schedule/schedule.controller.ts` declares `GET /schedule/today` 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 /schedule/work-modes

`backend/src/schedule/schedule.controller.ts` declares `GET /schedule/work-modes` 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 /users/:id

`backend/src/users/users.controller.ts` declares `GET /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 /users/:id/product-commissions

`backend/src/users/users.controller.ts` declares `GET /users/:id/product-commissions` 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: GET /users/dismissed

`backend/src/users/users.controller.ts` declares `GET /users/dismissed` 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 /users/masters

`backend/src/users/users.controller.ts` declares `GET /users/masters` 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 /employees/:id

`backend/src/employees/employees.controller.ts` declares `PATCH /employees/: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 /schedule/

`shared/api/createServices.ts` declares `PATCH /schedule/` 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 /schedule/:id

`backend/src/schedule/schedule.controller.ts` declares `PATCH /schedule/: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 /schedule/work-modes/:id

`backend/src/schedule/schedule.controller.ts` declares `PATCH /schedule/work-modes/: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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PATCH /users/:id

`backend/src/users/users.controller.ts` declares `PATCH /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 /warehouse/categories/order

`shared/api/createServices.ts` declares `PATCH /warehouse/categories/order` 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/logout

`shared/api/createServices.ts` declares `POST /auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /employees/:id/achievements

`backend/src/employees/employees.controller.ts` declares `POST /employees/:id/achievements` 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 /employees/:id/documents

`backend/src/employees/employees.controller.ts` declares `POST /employees/:id/documents` 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: POST /employees/:id/photo

`backend/src/employees/employees.controller.ts` declares `POST /employees/:id/photo` 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: POST /equipment/categories

`shared/api/createServices.ts` declares `POST /equipment/categories` 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 /equipment/issue

`shared/api/createServices.ts` declares `POST /equipment/issue` 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 /equipment/storage

`shared/api/createServices.ts` declares `POST /equipment/storage` 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 /expenses

`shared/api/createServices.ts` declares `POST /expenses` 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 /marketing/integrations/test

`shared/api/createServices.ts` declares `POST /marketing/integrations/test` 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 /marketing/sms/send

`shared/api/createServices.ts` declares `POST /marketing/sms/send` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/broadcast

`backend/src/notifications/notifications.controller.ts` declares `POST /notifications/broadcast` 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 /notifications/broadcasts/:id/seen

`backend/src/notifications/notifications.controller.ts` declares `POST /notifications/broadcasts/:id/seen` 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: POST /push/token

`shared/api/createServices.ts` declares `POST /push/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 consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /schedule/apply-work-mode

`backend/src/schedule/schedule.controller.ts` declares `POST /schedule/apply-work-mode` 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: POST /schedule/settings

`backend/src/schedule/schedule.controller.ts` declares `POST /schedule/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 i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /schedule/work-modes

`backend/src/schedule/schedule.controller.ts` declares `POST /schedule/work-modes` 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 /users/:id/product-commissions

`backend/src/users/users.controller.ts` declares `POST /users/:id/product-commissions` 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: POST /users/:id/purge

`backend/src/users/users.controller.ts` declares `POST /users/:id/purge` 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 /users/:id/restore

`backend/src/users/users.controller.ts` declares `POST /users/:id/restore` 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 /users/order

`shared/api/createServices.ts` declares `POST /users/order` 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 /

`frontend/public/sw.js` declares `PUT /` 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 /notifications/preferences

`backend/src/notifications/notifications.controller.ts` declares `PUT /notifications/preferences` 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 quality Complexity conf 1.00 Very large file: backend/src/checks/checks.service.ts (1345 lines)