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.

cc-team-8/mooimhacha

https://github.com/cc-team-8/mooimhacha · scanned 2026-06-17 01:46 UTC (1 month, 1 week ago)

86 raw signals (0 security + 86 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -26.5 (diff) · 76 actionable findings from 1 signal source. 10 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 · 76 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 16 Low 54 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 76 Crowd 0 Layer: Frontend 5 Hardware 3 Security 6 Cicd 1 Quality 11 Api 50

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 50.2/100 with 100.0% coverage. It contains 656 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 86 findings — concentrated in api (50), quality (17), hardware (6). Risk profile is high: 0 critical, 4 high, 22 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 74 of 76 actionable findings. 86 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: GET https://kapi.kakao.com/v2/user/me (server/src/auth/auth.service.ts:169)

`server/src/auth/auth.service.ts:169` calls `GET https://kapi.kakao.com/v2/user/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/kapi.kakao.com/v2/user/me` If this points at an external API, prefix it with …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (server/src/llm/llm.service.ts:157)

`server/src/llm/llm.service.ts:157` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an external API…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://kapi.kakao.com/v1/user/unlink (server/src/auth/auth.service.ts:247)

`server/src/auth/auth.service.ts:247` calls `POST https://kapi.kakao.com/v1/user/unlink` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/kapi.kakao.com/v1/user/unlink` If this points at an external API, prefix…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://kauth.kakao.com/oauth/token (server/src/auth/auth.service.ts:153)

`server/src/auth/auth.service.ts:153` calls `POST https://kauth.kakao.com/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/kauth.kakao.com/oauth/token` If this points at an external API, prefix it …

Dangling fetchFetch

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — client/src/lib/api.ts:26

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 — client/src/lib/auth.ts:10

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 — client/src/pages/meeting/ContributionDashboard.tsx:88

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 — server/src/auth/auth.service.ts:153

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph hardware Security conf 1.00 Dockerfile runs as root: client/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 4 occurrences Frontend route `/auth/callback` has no Link/navigate to it — client/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.

4 occurrences

repo-level (4 hits)

Orphan pageWiring

medium System graph quality Integrity conf 1.00 4 occurrences Frontend route `meeting` has no Link/navigate to it — client/src/pages/dashboard/DashboardPage.tsx

4 occurrences

repo-level (4 hits)

Orphan pageWiring

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in client/electron/preload/index.ts:93

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

client/electron/preload/index.ts:93 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in client/src/pages/dashboard/report/ReportPage.tsx:64

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

client/src/pages/dashboard/report/ReportPage.tsx:64 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in design/무임하차-elastic.html:2114

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

design/무임하차-elastic.html:2114 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in design/무임하차-web.html:1634

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

design/무임하차-web.html:1634 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in client/src/lib/api.ts:33

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

client/src/lib/api.ts:33 Local storage auth token

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in client/src/lib/auth.ts:22

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

client/src/lib/auth.ts:22 Local storage auth token

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

Found 19 placeholder/mock markers across 9 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 Tests conf 1.00 Very low test-to-source ratio

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

Coverage

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3

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

client/Dockerfile:33 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 4 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, 4 locations

server/Dockerfile:5, 11, 19 (3 hits)

client/Dockerfile:6

containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/setup-node@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 2 locations

.github/workflows/ci-client.yml:26

.github/workflows/ci-server.yml:26

CI/CD securitySupply chainGithub actions

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — client/src/components/Modal.tsx:26

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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — client/src/pages/meeting/AgendaTracker.tsx:150

Fq button no label

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — client/src/lib/apiFetch.ts:14

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — client/src/pages/onboarding/OnboardingPage.tsx:63

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/src/auth/auth.service.ts:57

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /action-items/:id

`server/src/action-items/action-items.controller.ts` declares `DELETE /action-items/: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 co…

Unused endpoint

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

`server/src/agendas/agendas.controller.ts` declares `DELETE /agendas/: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 /auth/me

`server/src/auth/auth.controller.ts` declares `DELETE /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: DELETE /decisions/:id

`server/src/decisions/decisions.controller.ts` declares `DELETE /decisions/: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 /meetings/:id

`server/src/meetings/meetings.controller.ts` declares `DELETE /meetings/: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 /meetings/:id/utterances/:utteranceId

`server/src/meetings/meetings.controller.ts` declares `DELETE /meetings/:id/utterances/:utteranceId` 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 /teams/:id

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /teams/:id/members/:userId

`server/src/teams/teams.controller.ts` declares `DELETE /teams/: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 documenting who consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /teams/:id/members/me

`server/src/teams/teams.controller.ts` declares `DELETE /teams/:id/members/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 /auth/kakao/callback

`server/src/auth/auth.controller.ts` declares `GET /auth/kakao/callback` 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/kakao/url

`server/src/auth/auth.controller.ts` declares `GET /auth/kakao/url` 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

`server/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 /meetings/:id

`server/src/meetings/meetings.controller.ts` declares `GET /meetings/: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 /meetings/:id/contributions

`server/src/contributions/contributions.controller.ts` declares `GET /meetings/:id/contributions` 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 /meetings/:id/report

`server/src/reports/reports.controller.ts` declares `GET /meetings/:id/report` 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 /meetings/:id/transcript

`server/src/meetings/meetings.controller.ts` declares `GET /meetings/:id/transcript` 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: GET /meetings/:meetingId/agendas

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /teams/:id

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /teams/:id/contributions

`server/src/contributions/contributions.controller.ts` declares `GET /teams/:id/contributions` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /teams/:id/settings

`server/src/teams/teams.controller.ts` declares `GET /teams/:id/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 /action-items/:id

`server/src/action-items/action-items.controller.ts` declares `PATCH /action-items/: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 /agendas/:id

`server/src/agendas/agendas.controller.ts` declares `PATCH /agendas/: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 /auth/profile

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

Unused endpoint

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

`server/src/decisions/decisions.controller.ts` declares `PATCH /decisions/: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 /meetings/:id

`server/src/meetings/meetings.controller.ts` declares `PATCH /meetings/: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 /meetings/:id/utterances/:utteranceId

`server/src/meetings/meetings.controller.ts` declares `PATCH /meetings/:id/utterances/:utteranceId` 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: PATCH /meetings/:id/utterances/batch

`server/src/meetings/meetings.controller.ts` declares `PATCH /meetings/:id/utterances/batch` 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: PATCH /notifications/:id/read

`server/src/notifications/notifications.controller.ts` declares `PATCH /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 or documenting…

Unused endpoint

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

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

Unused endpoint

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

`server/src/teams/teams.controller.ts` declares `PATCH /teams/:id/leader` 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 /teams/:id/settings

`server/src/teams/teams.controller.ts` declares `PATCH /teams/:id/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: POST /agendas/:id/activate

`server/src/agendas/agendas.controller.ts` declares `POST /agendas/:id/activate` 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 /agendas/:id/summarize

`server/src/agendas/agendas.controller.ts` declares `POST /agendas/:id/summarize` 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/kakao

`server/src/auth/auth.controller.ts` declares `POST /auth/kakao` 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

`server/src/auth/auth.controller.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 /auth/refresh

`server/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 /meetings/:id/confirm

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /meetings/:id/contributions/recompute

`server/src/meetings/meetings.controller.ts` declares `POST /meetings/:id/contributions/recompute` 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 document…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /meetings/:id/end

`server/src/meetings/meetings.controller.ts` declares `POST /meetings/:id/end` 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 /meetings/:id/start

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /meetings/:id/summarize

`server/src/meetings/meetings.controller.ts` declares `POST /meetings/:id/summarize` 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 /meetings/:meetingId/agendas

`server/src/agendas/agendas.controller.ts` declares `POST /meetings/:meetingId/agendas` 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 /meetings/:meetingId/agendas/generate

`server/src/agendas/agendas.controller.ts` declares `POST /meetings/:meetingId/agendas/generate` 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/read-all

`server/src/notifications/notifications.controller.ts` declares `POST /notifications/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 — consider removing or documenting …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /teams/:id/invite-code

`server/src/teams/teams.controller.ts` declares `POST /teams/:id/invite-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 consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /teams/join

`server/src/teams/teams.controller.ts` declares `POST /teams/join` 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

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/73a9d868-c5a1-4648-8ac3-c3ea4f95cc31/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/73a9d868-c5a1-4648-8ac3-c3ea4f95cc31/

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.