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

semaphore-chat/semaphore-chat

https://github.com/semaphore-chat/semaphore-chat · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

245 raw signals (0 security + 245 graph)

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

Complete repo analysis

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

JSON
Combined
56.2
/100
Security checks
56
0 findings
System graph
56
100.0% cov · 123 findings
Critical
15
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 15 High 4 Medium 19 Low 70 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 123 Crowd 0 Layer: Frontend 12 Hardware 4 Security 21 Cicd 5 Quality 27 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 56.2/100 with 100.0% coverage. It contains 3549 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 245 findings — concentrated in cicd (82), api (54), security (48). Risk profile is high: 42 critical, 4 high, 72 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 5 occurrences Possible secret in backend/prisma/seed-e2e.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 20, 27, 34, 45, 53
backend/prisma/seed-e2e.ts:20, 27, 34, 45, 53 (5 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in frontend/src/components/Onboarding/AdminSetupStep.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 58, 60
frontend/src/components/Onboarding/AdminSetupStep.tsx:58, 60 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in helm/semaphore-chat/README.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
helm/semaphore-chat/README.md:197
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in helm/semaphore-chat/values.yaml
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 319, 320
helm/semaphore-chat/values.yaml:319, 320 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/api/messages/channel/ch-err (frontend/src/__tests__/integration/queryHooks.test.ts:44)
`frontend/src/__tests__/integration/queryHooks.test.ts:44` calls `GET http://localhost:3000/api/messages/channel/ch-err` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3000/api/messages/channel/ch-er…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/api/messages/channel/ch-msw?limit=25&continuationToken= (frontend/src/__tests__/integration/queryHooks.test.ts:24)
`frontend/src/__tests__/integration/queryHooks.test.ts:24` calls `GET http://localhost:3000/api/messages/channel/ch-msw?limit=25&continuationToken=` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:300…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/api/messages/group/dm-msw?limit=25&continuationToken= (frontend/src/__tests__/integration/queryHooks.test.ts:58)
`frontend/src/__tests__/integration/queryHooks.test.ts:58` calls `GET http://localhost:3000/api/messages/group/dm-msw?limit=25&continuationToken=` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3000/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/api/threads/parent-msw/replies (frontend/src/__tests__/integration/queryHooks.test.ts:73)
`frontend/src/__tests__/integration/queryHooks.test.ts:73` calls `GET http://localhost:3000/api/threads/parent-msw/replies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3000/api/threads/parent-msw/…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/__tests__/integration/queryHooks.test.ts:24
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/api-client-config.ts:37
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useAuthenticatedFile.ts:73
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useDebugPanel.ts:20
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. 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 quality Integrity conf 1.00 Frontend route `/community/:communityId/channel/:channelId` has no Link/navigate to it — frontend/src/__tests__/components/AuthGate.test.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 quality Integrity conf 1.00 19 occurrences Frontend route `/join/:inviteCode` 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.
19 occurrences
repo-level (19 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 30 occurrences GitHub Action is tag-pinned rather than SHA-pinned
pnpm/action-setup@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
8 files, 30 locations
.github/workflows/docker-publish.yml:63, 67, 75, 89, 107, 121, 168, 172, +4 more (12 hits)
.github/workflows/e2e-tests.yml:29, 60, 101, 104, 251, 288, 291 (7 hits)
.github/workflows/backend-tests.yml:27, 56, 113, 214 (4 hits)
.github/workflows/electron-build.yml:41, 80, 164 (3 hits)
.github/workflows/dependabot-auto-merge.yml:18
.github/workflows/frontend-tests.yml:29
.github/workflows/helm-publish.yml:55
.github/workflows/security-audit.yml:19
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 7 occurrences 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.
7 files, 7 locations
.github/workflows/backend-tests.yml
.github/workflows/dependabot-auto-merge.yml
.github/workflows/deploy-docs.yml
.github/workflows/docker-publish.yml
.github/workflows/electron-build.yml
.github/workflows/frontend-tests.yml
.github/workflows/helm-publish.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/utils/tokenService.ts:174
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/utils/tokenService.ts:174 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/storage-quota/storage-quota.service.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/storage-quota/storage-quota.service.ts:4 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 128 placeholder/mock markers across 46 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 64 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: node:24-slim
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:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:24-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 43 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.
7 files, 43 locations
.github/workflows/electron-build.yml:38, 44, 77, 83, 90, 131, 138, 145, +9 more (17 hits)
.github/workflows/e2e-tests.yml:27, 57, 63, 76, 209, 217, 248, 254, +3 more (11 hits)
.github/workflows/backend-tests.yml:24, 30, 53, 59, 110, 116, 211, 217 (8 hits)
.github/workflows/docker-publish.yml:37, 142 (2 hits)
.github/workflows/frontend-tests.yml:26, 32 (2 hits)
.github/workflows/security-audit.yml:16, 22 (2 hits)
.github/workflows/helm-publish.yml:34
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
168 tests / 802 src (ratio 0.21).
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: backend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: frontend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: shared/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
shared/package.json LockfileReproducibilityGenerated 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 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.
backend/package.json CI/CD securitySupply chainNpm
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/prisma/migrate-instance-roles.ts:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/prisma/seed-e2e.ts:93
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/prisma/seed.ts:58
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/generate-openapi.ts: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 — frontend/electron/main.ts:66
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/sw-custom.ts:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/utils/logger.ts:20
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 /alias-groups/:groupId
`backend/src/alias-groups/alias-groups.controller.ts` declares `DELETE /alias-groups/:groupId` 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: DELETE /alias-groups/:groupId/members/:userId
`backend/src/alias-groups/alias-groups.controller.ts` declares `DELETE /alias-groups/:groupId/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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /auth/sessions
`backend/src/auth/auth.controller.ts` declares `DELETE /auth/sessions` 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/sessions/:sessionId
`backend/src/auth/auth.controller.ts` declares `DELETE /auth/sessions/:sessionId` 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: DELETE /invite/:code
`backend/src/invite/invite.controller.ts` declares `DELETE /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: DELETE /notifications/:id
`backend/src/notifications/notifications.controller.ts` declares `DELETE /notifications/: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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /notifications/channels/:channelId/override
`backend/src/notifications/notifications.controller.ts` declares `DELETE /notifications/channels/:channelId/override` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /notifications/debug/clear-all
`backend/src/notifications/notifications.controller.ts` declares `DELETE /notifications/debug/clear-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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /push/unsubscribe
`backend/src/push-notifications/push-notifications.controller.ts` declares `DELETE /push/unsubscribe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /threads/:parentMessageId/subscribe
`backend/src/threads/threads.controller.ts` declares `DELETE /threads/:parentMessageId/subscribe` 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 /alias-groups/:groupId
`backend/src/alias-groups/alias-groups.controller.ts` declares `GET /alias-groups/:groupId` 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 /alias-groups/community/:communityId
`backend/src/alias-groups/alias-groups.controller.ts` declares `GET /alias-groups/community/:communityId` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/sessions
`backend/src/auth/auth.controller.ts` declares `GET /auth/sessions` 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 /channels/:channelId/voice-presence/me
`backend/src/voice-presence/voice-presence.controller.ts` declares `GET /channels/:channelId/voice-presence/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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /instance/settings
`backend/src/instance/instance.controller.ts` declares `GET /instance/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 /instance/settings/public
`backend/src/instance/instance.controller.ts` declares `GET /instance/settings/public` 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 /instance/stats
`backend/src/instance/instance.controller.ts` declares `GET /instance/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 /invite/:code
`backend/src/invite/invite.controller.ts` declares `GET /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: GET /invite/public/:code
`backend/src/invite/invite.controller.ts` declares `GET /invite/public/: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: GET /notifications/channels/:channelId/override
`backend/src/notifications/notifications.controller.ts` declares `GET /notifications/channels/:channelId/override` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/debug/subscriptions
`backend/src/notifications/notifications.controller.ts` declares `GET /notifications/debug/subscriptions` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/settings
`backend/src/notifications/notifications.controller.ts` declares `GET /notifications/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/unread-count
`backend/src/notifications/notifications.controller.ts` declares `GET /notifications/unread-count` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /push/status
`backend/src/push-notifications/push-notifications.controller.ts` declares `GET /push/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /push/vapid-public-key
`backend/src/push-notifications/push-notifications.controller.ts` declares `GET /push/vapid-public-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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /threads/:parentMessageId/metadata
`backend/src/threads/threads.controller.ts` declares `GET /threads/:parentMessageId/metadata` 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 /threads/:parentMessageId/replies
`backend/src/threads/threads.controller.ts` declares `GET /threads/:parentMessageId/replies` 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 /instance/settings
`backend/src/instance/instance.controller.ts` declares `PATCH /instance/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /alias-groups/:groupId/members
`backend/src/alias-groups/alias-groups.controller.ts` declares `POST /alias-groups/:groupId/members` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /alias-groups/community/:communityId
`backend/src/alias-groups/alias-groups.controller.ts` declares `POST /alias-groups/community/:communityId` 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 /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
`backend/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
`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 /channels/:channelId/voice-presence/deafen
`backend/src/voice-presence/voice-presence.controller.ts` declares `POST /channels/:channelId/voice-presence/deafen` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /channels/:channelId/voice-presence/join
`backend/src/voice-presence/voice-presence.controller.ts` declares `POST /channels/:channelId/voice-presence/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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /channels/:channelId/voice-presence/leave
`backend/src/voice-presence/voice-presence.controller.ts` declares `POST /channels/:channelId/voice-presence/leave` 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 rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /channels/:channelId/voice-presence/refresh
`backend/src/voice-presence/voice-presence.controller.ts` declares `POST /channels/:channelId/voice-presence/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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/:id/dismiss
`backend/src/notifications/notifications.controller.ts` declares `POST /notifications/:id/dismiss` 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 /notifications/:id/read
`backend/src/notifications/notifications.controller.ts` declares `POST /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: POST /notifications/debug/send-test
`backend/src/notifications/notifications.controller.ts` declares `POST /notifications/debug/send-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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/read-all
`backend/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 /push/debug/send-test
`backend/src/push-notifications/push-notifications.controller.ts` declares `POST /push/debug/send-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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /push/subscribe
`backend/src/push-notifications/push-notifications.controller.ts` declares `POST /push/subscribe` 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: POST /push/test
`backend/src/push-notifications/push-notifications.controller.ts` declares `POST /push/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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /threads/:parentMessageId/replies
`backend/src/threads/threads.controller.ts` declares `POST /threads/:parentMessageId/replies` 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: POST /threads/:parentMessageId/subscribe
`backend/src/threads/threads.controller.ts` declares `POST /threads/:parentMessageId/subscribe` 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: PUT /alias-groups/:groupId
`backend/src/alias-groups/alias-groups.controller.ts` declares `PUT /alias-groups/:groupId` 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: PUT /alias-groups/:groupId/members
`backend/src/alias-groups/alias-groups.controller.ts` declares `PUT /alias-groups/:groupId/members` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /notifications/channels/:channelId/override
`backend/src/notifications/notifications.controller.ts` declares `PUT /notifications/channels/:channelId/override` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /notifications/settings
`backend/src/notifications/notifications.controller.ts` declares `PUT /notifications/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 …
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/src/notifications/notifications.service.spec.ts (1738 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/src/roles/roles.service.spec.ts (2035 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/176b786f-36cf-4c06-b7b5-56afeebfa7cc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/176b786f-36cf-4c06-b7b5-56afeebfa7cc/

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.