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

safe-global/safe-client-gateway

https://github.com/safe-global/safe-client-gateway · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

265 raw signals (116 security + 149 graph)

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

Complete repo analysis

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

JSON
Combined
55.6
/100
Security checks
56
9 findings
System graph
56
100.0% cov · 148 findings
Critical
3
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 3 Medium 11 Low 83 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 148 Crowd 0 Layer: Quality 50 Security 4 Frontend 47 Network 1 Hardware 3 Cicd 2 Api 50
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 55.6/100 with 100.0% coverage. It contains 4495 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 149 findings — concentrated in api (50), frontend (47), quality (42). Risk profile is high: 1 critical, 0 high, 7 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 95 of 157 actionable findings. 528 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 quality Practices conf 0.82 17 occurrences Foundry mined mock as real or placeholder: safe-global/safe-client-gateway
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
17 occurrences
repo-level (17 hits)
critical Security checks security auth conf 0.78 19 occurrences Foundry mined security auth guardrail gaps: safe-global/safe-client-gateway
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…
19 occurrences
repo-level (19 hits)
high Security checks quality Practices conf 0.84 32 occurrences Foundry mined bad chains: safe-global/safe-client-gateway
Comment chain pattern product: bad_chains Repo: safe-global/safe-client-gateway Thread: safe-global/safe-client-gateway:github-feedback-comment-d11cc148b27d57a9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_sig…
32 occurrences
repo-level (32 hits)
high Security checks quality Quality conf 0.76 17 occurrences Foundry mined schema ui api mismatch: safe-global/safe-client-gateway
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: assumption_check Repo: safe-global/sa…
17 occurrences
repo-level (17 hits)
high Security checks quality Testing conf 0.78 24 occurrences Foundry mined test ci gap after feedback: safe-global/safe-client-gateway
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: …
24 occurrences
repo-level (24 hits)
medium Security checks quality Practices conf 0.62 111 occurrences Foundry mined assumption checks: safe-global/safe-client-gateway
Comment chain pattern product: assumption_checks Repo: safe-global/safe-client-gateway Thread: safe-global/safe-client-gateway:github-feedback-comment-eeb010841948045a Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_backed_multi_signal_gra…
111 occurrences
repo-level (111 hits)
medium Security checks quality maintenance conf 0.70 74 occurrences Foundry mined blueprint gap alignment: safe-global/safe-client-gateway
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: …
74 occurrences
repo-level (74 hits)
medium Security checks quality Practices conf 0.72 4 occurrences Foundry mined review feedback without structured fix: safe-global/safe-client-gateway
Graph query export: Review feedback without structured fix chain Query id: review_feedback_without_structured_fix Query type: motif_query Intent: Weak-supervision examples for review comments lacking a traceable fix. Motif: review_feedback_without_structured_fix Training usage: weak_supervision Gra…
4 occurrences
repo-level (4 hits)
medium Security checks quality Practices conf 0.70 81 occurrences Foundry mined unresolved feedback: safe-global/safe-client-gateway
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: need…
81 occurrences
repo-level (81 hits)
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: .devcontainer/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/claude-code-review.yml CI/CD securitySupply chainGithub actions
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 26 placeholder/mock markers across 14 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 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.devcontainer/Dockerfile Ports
low System graph quality Maintenance conf 1.00 111 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
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 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:24.11.0-alpine3.21
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 4, 21
Dockerfile:4, 21 (2 hits)
containersPinned dependencies
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cacheResult_1_old` in src/modules/notifications/domain/v2/notifications.repository.integration.spec.ts:359
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `extraVarsDeprecated` in scripts/validate-env-json.ts:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `master_copy` in migrations/1775500000000-create-counterfactual-safes.ts:21
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `master_copy` in src/modules/counterfactual-safes/datasources/entities/counterfactual-safe.entity.db.ts:51
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/validation/entities/raw.entity.ts:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id
`src/modules/spaces/routes/spaces.controller.ts` declares `DELETE /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:spaceId/address-book/:address
`src/modules/spaces/routes/address-books.controller.ts` declares `DELETE /:spaceId/address-book/:address` 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: DELETE /:spaceId/members
`src/modules/spaces/routes/members.controller.ts` declares `DELETE /:spaceId/members` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:spaceId/members/:userId
`src/modules/spaces/routes/members.controller.ts` declares `DELETE /:spaceId/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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /chains/:chainId/notifications/devices/:deviceUuid
`src/modules/notifications/routes/v2/notifications.controller.ts` declares `DELETE /chains/:chainId/notifications/devices/:deviceUuid` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /chains/:chainId/notifications/devices/:uuid
`src/modules/notifications/routes/v1/notifications.controller.ts` declares `DELETE /chains/:chainId/notifications/devices/:uuid` 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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /chains/:chainId/notifications/devices/:uuid/safes/:safeAddress
`src/modules/notifications/routes/v1/notifications.controller.ts` declares `DELETE /chains/:chainId/notifications/devices/:uuid/safes/:safeAddress` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /chains/:chainId/transactions/:safeTxHash
`src/modules/transactions/routes/transactions.controller.ts` declares `DELETE /chains/:chainId/transactions/:safeTxHash` 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 — conside…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /notifications/subscriptions
`src/modules/notifications/routes/v2/notifications.controller.ts` declares `DELETE /notifications/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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /wallet/:walletAddress
`src/modules/users/routes/users.controller.ts` declares `DELETE /wallet/:walletAddress` 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 /:id
`src/modules/spaces/routes/spaces.controller.ts` declares `GET /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:safeAddress
`src/modules/relay/routes/relay.controller.ts` declares `GET /:safeAddress` 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 /:spaceId/address-book
`src/modules/spaces/routes/address-books.controller.ts` declares `GET /:spaceId/address-book` 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 /:spaceId/address-book/requests
`src/modules/spaces/routes/address-book-requests.controller.ts` declares `GET /:spaceId/address-book/requests` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:spaceId/audit-log
`src/modules/spaces/routes/space-audit.controller.ts` declares `GET /:spaceId/audit-log` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:spaceId/audit-log/actors
`src/modules/spaces/routes/space-audit.controller.ts` declares `GET /:spaceId/audit-log/actors` 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 /:spaceId/members
`src/modules/spaces/routes/members.controller.ts` declares `GET /:spaceId/members` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:spaceId/membership
`src/modules/spaces/routes/members.controller.ts` declares `GET /:spaceId/membership` 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 /chains/:chainId/multisig-transactions/:safeTxHash/raw
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/multisig-transactions/:safeTxHash/raw` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/notifications/devices/:deviceUuid/safes/:safeAddress
`src/modules/notifications/routes/v2/notifications.controller.ts` declares `GET /chains/:chainId/notifications/devices/:deviceUuid/safes/:safeAddress` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Othe…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/owners/:ownerAddress/safes
`src/modules/owners/routes/owners.controller.v1.ts` declares `GET /chains/:chainId/owners/:ownerAddress/safes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/collectibles
`src/modules/collectibles/routes/collectibles.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/collectibles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/creation/raw
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/creation/raw` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/incoming-transfers
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/incoming-transfers` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/module-transactions
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/module-transactions` 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 cod…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/multisig-transactions
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/multisig-transactions` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/multisig-transactions/raw
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/multisig-transactions/raw` 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 de…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/positions/:fiatCode
`src/modules/positions/routes/positions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/positions/:fiatCode` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/transactions/creation
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/transactions/creation` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/transactions/history
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/transactions/history` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /chains/:chainId/safes/:safeAddress/transactions/queued
`src/modules/transactions/routes/transactions.controller.ts` declares `GET /chains/:chainId/safes/:safeAddress/transactions/queued` 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 cod…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /owners/:ownerAddress/safes
`src/modules/owners/routes/owners.controller.v2.ts` declares `GET /owners/:ownerAddress/safes` 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 /:id
`src/modules/spaces/routes/spaces.controller.ts` declares `PATCH /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:spaceId/members/:userId/role
`src/modules/spaces/routes/members.controller.ts` declares `PATCH /:spaceId/members/:userId/role` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:spaceId/members/alias
`src/modules/spaces/routes/members.controller.ts` declares `PATCH /:spaceId/members/alias` 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 /:spaceId/address-book/requests
`src/modules/spaces/routes/address-book-requests.controller.ts` declares `POST /:spaceId/address-book/requests` 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: POST /:spaceId/members/:userId/invite/renew
`src/modules/spaces/routes/members.controller.ts` declares `POST /:spaceId/members/:userId/invite/renew` 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: POST /:spaceId/members/accept
`src/modules/spaces/routes/members.controller.ts` declares `POST /:spaceId/members/accept` 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 /:spaceId/members/decline
`src/modules/spaces/routes/members.controller.ts` declares `POST /:spaceId/members/decline` 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 /:spaceId/members/invite
`src/modules/spaces/routes/members.controller.ts` declares `POST /:spaceId/members/invite` 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 /chains/:chainId/transactions/:safeAddress/preview
`src/modules/transactions/routes/transactions.controller.ts` declares `POST /chains/:chainId/transactions/:safeAddress/preview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /chains/:chainId/transactions/:safeAddress/propose
`src/modules/transactions/routes/transactions.controller.ts` declares `POST /chains/:chainId/transactions/:safeAddress/propose` 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 — …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /chains/:chainId/transactions/:safeTxHash/confirmations
`src/modules/transactions/routes/transactions.controller.ts` declares `POST /chains/:chainId/transactions/:safeTxHash/confirmations` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /create-with-user
`src/modules/spaces/routes/spaces.controller.ts` declares `POST /create-with-user` 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 /register/notifications
`src/modules/notifications/routes/v2/notifications.controller.ts` declares `POST /register/notifications` 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: POST /wallet
`src/modules/users/routes/users.controller.ts` declares `POST /wallet` 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 /wallet/add
`src/modules/users/routes/users.controller.ts` declares `POST /wallet/add` 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 /:spaceId/address-book
`src/modules/spaces/routes/address-books.controller.ts` declares `PUT /:spaceId/address-book` 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: PUT /:spaceId/address-book/requests/:requestId/approve
`src/modules/spaces/routes/address-book-requests.controller.ts` declares `PUT /:spaceId/address-book/requests/:requestId/approve` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:spaceId/address-book/requests/:requestId/reject
`src/modules/spaces/routes/address-book-requests.controller.ts` declares `PUT /:spaceId/address-book/requests/:requestId/reject` 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 —…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/modules/messages/routes/messages.controller.integration.spec.ts (1834 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/notifications/domain/push/push-notification.integration.spec.ts (1575 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/notifications/domain/v2/notifications.repository.integration.spec.ts (1434 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/relay/domain/limit-addresses.mapper.spec.ts (1627 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/relay/routes/relay.controller.integration.spec.ts (3611 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/safe-shield/contract-analysis/contract-analysis.service.spec.ts (1676 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/safe-shield/deadlock-analysis/deadlock-analysis.service.spec.ts (1607 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/safe-shield/recipient-analysis/recipient-analysis.service.spec.ts (1820 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/safe-shield/safe-shield.service.spec.ts (1799 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/safe/routes/safes.controller.integration.spec.ts (2393 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/safe/routes/safes.controller.overview.integration.spec.ts (1846 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/spaces/routes/members.controller.e2e-spec.ts (2046 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/datasources/transaction-api.service.spec.ts (2982 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/__tests__/controllers/get-transaction-by-id.transactions.controller.integration.spec.ts (1532 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/__tests__/controllers/preview-transaction-kiln.transactions.controller.integration.spec.ts (2471 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/__tests__/controllers/propose-transaction.transactions.controller.integration.spec.ts (1775 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/helpers/transaction-verifier.helper.spec.ts (2372 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/mappers/common/twap-order.mapper.spec.ts (1726 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/transactions-history.controller.integration.spec.ts (1577 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/transactions/routes/transactions-history.imitation-transactions.controller.integration.spec.ts (4423 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/modules/users/domain/members.repository.integration.spec.ts (3763 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/f927b54a-d3d2-4212-83bb-c76fda5b3e07/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f927b54a-d3d2-4212-83bb-c76fda5b3e07/

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.