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

blakebauman/edgevault

https://github.com/blakebauman/edgevault · scanned 2026-06-17 01:41 UTC (1 month, 1 week ago)

205 raw signals (0 security + 205 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -11.8 (diff) · 205 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
64.9
/100
Security checks
65
0 findings
System graph
65
100.0% cov · 205 findings
Critical
2
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 2 High 67 Medium 49 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 205 Crowd 0 Layer: Frontend 3 Security 5 Cicd 1 Quality 79 Api 117
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 64.9/100 with 100.0% coverage. It contains 1462 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 205 findings — concentrated in api (117), quality (79), security (5). Risk profile is high: 2 critical, 67 high, 49 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 192 of 205 actionable findings. 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://api.cloudflare.com/client/v4/zones/${config.zoneId}/custom_hostnames${path} (apps/api/src/custom-hostnames.ts:120)
`apps/api/src/custom-hostnames.ts:120` calls `GET https://api.cloudflare.com/client/v4/zones/${config.zoneId}/custom_hostnames${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/billing.tsx:36)
`apps/console/app/routes/billing.tsx:36` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/domains.tsx:70)
`apps/console/app/routes/domains.tsx:70` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/home.tsx:30)
`apps/console/app/routes/home.tsx:30` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/members.tsx:65)
`apps/console/app/routes/members.tsx:65` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/saml-admin.tsx:35)
`apps/console/app/routes/saml-admin.tsx:35` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/scim.tsx:28)
`apps/console/app/routes/scim.tsx:28` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations (apps/console/app/routes/sso-admin.tsx:36)
`apps/console/app/routes/sso-admin.tsx:36` calls `GET https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations/${org.id}/workspaces (apps/console/app/routes/home.tsx:54)
`apps/console/app/routes/home.tsx:54` calls `GET https://api/api/v1/organizations/${org.id}/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/workspaces` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations/${params.orgId}/domains (apps/console/app/routes/domains.tsx:82)
`apps/console/app/routes/domains.tsx:82` calls `GET https://api/api/v1/organizations/${params.orgId}/domains` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/domains` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations/${params.orgId}/invitations (apps/console/app/routes/members.tsx:88)
`apps/console/app/routes/members.tsx:88` calls `GET https://api/api/v1/organizations/${params.orgId}/invitations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/invitations` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations/${params.orgId}/members (apps/console/app/routes/members.tsx:74)
`apps/console/app/routes/members.tsx:74` calls `GET https://api/api/v1/organizations/${params.orgId}/members` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/members` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations/${params.orgId}/scim-token (apps/console/app/routes/scim.tsx:39)
`apps/console/app/routes/scim.tsx:39` calls `GET https://api/api/v1/organizations/${params.orgId}/scim-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/scim-token` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/organizations/${params.orgId}/security (apps/console/app/routes/members.tsx:91)
`apps/console/app/routes/members.tsx:91` calls `GET https://api/api/v1/organizations/${params.orgId}/security` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/security` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/workspaces${path} (apps/console/app/routes/dashboard.notifications.tsx:56)
`apps/console/app/routes/dashboard.notifications.tsx:56` calls `GET https://api/api/v1/workspaces${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p>` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/workspaces${path} (apps/console/app/routes/environment.tsx:87)
`apps/console/app/routes/environment.tsx:87` calls `GET https://api/api/v1/workspaces${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p>` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/workspaces/${encodeURIComponent(body.workspaceId)} (apps/console/app/routes/api.reveal-token.tsx:40)
`apps/console/app/routes/api.reveal-token.tsx:40` calls `GET https://api/api/v1/workspaces/${encodeURIComponent(body.workspaceId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p>` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api/api/v1/workspaces/${workspaceId} (apps/console/app/lib/workspace.server.ts:15)
`apps/console/app/lib/workspace.server.ts:15` calls `GET https://api/api/v1/workspaces/${workspaceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p>` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://auth${path} (apps/console/app/routes/account-mfa.tsx:19)
`apps/console/app/routes/account-mfa.tsx:19` calls `GET https://auth${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://auth.internal/.well-known/jwks.json (apps/api/src/middleware/auth.ts:22)
`apps/api/src/middleware/auth.ts:22` calls `GET https://auth.internal/.well-known/jwks.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth.internal/.well-known/jwks.json` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://auth/me (apps/console/app/routes/home.tsx:33)
`apps/console/app/routes/home.tsx:33` calls `GET https://auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://auth/orgs/${params.orgId}/saml/connection (apps/console/app/routes/saml-admin.tsx:58)
`apps/console/app/routes/saml-admin.tsx:58` calls `GET https://auth/orgs/${params.orgId}/saml/connection` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/saml/connection` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://auth/orgs/${params.orgId}/sso/connection (apps/console/app/routes/sso-admin.tsx:57)
`apps/console/app/routes/sso-admin.tsx:57` calls `GET https://auth/orgs/${params.orgId}/sso/connection` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/sso/connection` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://billing/billing/status?organizationId=${params.orgId} (apps/console/app/routes/billing.tsx:58)
`apps/console/app/routes/billing.tsx:58` calls `GET https://billing/billing/status?organizationId=${params.orgId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/billing/billing/status` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://api/api/v1/organizations/${params.orgId}/security (apps/console/app/routes/members.tsx:178)
`apps/console/app/routes/members.tsx:178` calls `PATCH https://api/api/v1/organizations/${params.orgId}/security` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/security` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/passkey (apps/console/app/lib/passkey.ts:15)
`apps/console/app/lib/passkey.ts:15` calls `POST /api/passkey` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/passkey` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/reveal-token (apps/console/app/lib/passkey.ts:58)
`apps/console/app/lib/passkey.ts:58` calls `POST /api/reveal-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/reveal-token` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/${encodeURIComponent(workspaceId)}/assistant (apps/console/app/lib/use-agent-chat.ts:58)
`apps/console/app/lib/use-agent-chat.ts:58` calls `POST /dashboard/${encodeURIComponent(workspaceId)}/assistant` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/<p>/assistant` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/api/v1/organizations (apps/console/app/routes/home.tsx:92)
`apps/console/app/routes/home.tsx:92` calls `POST https://api/api/v1/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations` 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/api/v1/organizations/${orgId}/workspaces (apps/console/app/routes/home.tsx:103)
`apps/console/app/routes/home.tsx:103` calls `POST https://api/api/v1/organizations/${orgId}/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/workspaces` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/api/v1/organizations/${params.orgId}/invitations/${id}/resend (apps/console/app/routes/members.tsx:139)
`apps/console/app/routes/members.tsx:139` calls `POST https://api/api/v1/organizations/${params.orgId}/invitations/${id}/resend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/organizations/<p>/inv…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/api/v1/shares (apps/console/app/routes/share.tsx:30)
`apps/console/app/routes/share.tsx:30` calls `POST https://api/api/v1/shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/shares` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/api/v1/workspaces/${params.workspaceId}/assistant (apps/console/app/routes/assistant.tsx:32)
`apps/console/app/routes/assistant.tsx:32` calls `POST https://api/api/v1/workspaces/${params.workspaceId}/assistant` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p>/assistant` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/api/v1/workspaces/${params.workspaceId}/promotion-workflows (apps/console/app/routes/dashboard.compare.tsx:114)
`apps/console/app/routes/dashboard.compare.tsx:114` calls `POST https://api/api/v1/workspaces/${params.workspaceId}/promotion-workflows` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/api/v1/workspaces/${params.workspaceId}/promotion-workflows (apps/console/app/routes/dashboard.compare.tsx:136)
`apps/console/app/routes/dashboard.compare.tsx:136` calls `POST https://api/api/v1/workspaces/${params.workspaceId}/promotion-workflows` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/api/v1/workspaces/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api/internal/shares/${params.id}/consume (apps/console/app/routes/share.view.tsx:21)
`apps/console/app/routes/share.view.tsx:21` calls `POST https://api/internal/shares/${params.id}/consume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api/internal/shares/<p>/consume` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth${path} (apps/console/app/routes/login.mfa.tsx:40)
`apps/console/app/routes/login.mfa.tsx:40` calls `POST https://auth${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth${path} (apps/console/app/routes/login.tsx:49)
`apps/console/app/routes/login.tsx:49` calls `POST https://auth${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/internal/sso/provision (apps/console/app/routes/saml.acs.tsx:36)
`apps/console/app/routes/saml.acs.tsx:36` calls `POST https://auth/internal/sso/provision` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/internal/sso/provision` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/internal/sso/provision (apps/console/app/routes/sso.callback.tsx:43)
`apps/console/app/routes/sso.callback.tsx:43` calls `POST https://auth/internal/sso/provision` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/internal/sso/provision` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/oauth/${provider}/callback (apps/console/app/routes/oauth.callback.tsx:26)
`apps/console/app/routes/oauth.callback.tsx:26` calls `POST https://auth/oauth/${provider}/callback` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/oauth/<p>/callback` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/oauth/${provider}/start (apps/console/app/routes/oauth.start.tsx:17)
`apps/console/app/routes/oauth.start.tsx:17` calls `POST https://auth/oauth/${provider}/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/oauth/<p>/start` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/orgs/${orgId}/saml/acs (apps/console/app/routes/saml.acs.tsx:27)
`apps/console/app/routes/saml.acs.tsx:27` calls `POST https://auth/orgs/${orgId}/saml/acs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/saml/acs` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/orgs/${orgId}/saml/start (apps/console/app/routes/saml.start.tsx:15)
`apps/console/app/routes/saml.start.tsx:15` calls `POST https://auth/orgs/${orgId}/saml/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/saml/start` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/orgs/${orgId}/sso/callback (apps/console/app/routes/sso.callback.tsx:28)
`apps/console/app/routes/sso.callback.tsx:28` calls `POST https://auth/orgs/${orgId}/sso/callback` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/sso/callback` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/orgs/${orgId}/sso/start (apps/console/app/routes/sso.start.tsx:16)
`apps/console/app/routes/sso.start.tsx:16` calls `POST https://auth/orgs/${orgId}/sso/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/sso/start` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/password/forgot (apps/console/app/routes/forgot-password.tsx:15)
`apps/console/app/routes/forgot-password.tsx:15` calls `POST https://auth/password/forgot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/password/forgot` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/password/reset (apps/console/app/routes/reset-password.tsx:22)
`apps/console/app/routes/reset-password.tsx:22` calls `POST https://auth/password/reset` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/password/reset` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/reauth (apps/console/app/routes/api.reveal-token.tsx:102)
`apps/console/app/routes/api.reveal-token.tsx:102` calls `POST https://auth/reauth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/reauth` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/reauth (apps/console/app/routes/api.reveal-token.tsx:69)
`apps/console/app/routes/api.reveal-token.tsx:69` calls `POST https://auth/reauth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/reauth` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/token (apps/console/app/routes/api.passkey.tsx:110)
`apps/console/app/routes/api.passkey.tsx:110` calls `POST https://auth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/token` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/token (apps/console/app/routes/login.mfa.tsx:49)
`apps/console/app/routes/login.mfa.tsx:49` calls `POST https://auth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/token` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/token (apps/console/app/routes/login.tsx:69)
`apps/console/app/routes/login.tsx:69` calls `POST https://auth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/token` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/token (apps/console/app/routes/oauth.callback.tsx:39)
`apps/console/app/routes/oauth.callback.tsx:39` calls `POST https://auth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/token` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/token (apps/console/app/routes/saml.acs.tsx:45)
`apps/console/app/routes/saml.acs.tsx:45` calls `POST https://auth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/token` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/token (apps/console/app/routes/sso.callback.tsx:52)
`apps/console/app/routes/sso.callback.tsx:52` calls `POST https://auth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/token` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/verify-email (apps/console/app/routes/verify-email.tsx:19)
`apps/console/app/routes/verify-email.tsx:19` calls `POST https://auth/verify-email` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/verify-email` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/verify-email/resend (apps/console/app/routes/home.tsx:76)
`apps/console/app/routes/home.tsx:76` calls `POST https://auth/verify-email/resend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/verify-email/resend` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/webauthn/auth/options (apps/console/app/routes/api.passkey.tsx:77)
`apps/console/app/routes/api.passkey.tsx:77` calls `POST https://auth/webauthn/auth/options` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/webauthn/auth/options` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/webauthn/auth/options (apps/console/app/routes/api.reveal-token.tsx:52)
`apps/console/app/routes/api.reveal-token.tsx:52` calls `POST https://auth/webauthn/auth/options` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/webauthn/auth/options` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/webauthn/auth/verify (apps/console/app/routes/api.passkey.tsx:92)
`apps/console/app/routes/api.passkey.tsx:92` calls `POST https://auth/webauthn/auth/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/webauthn/auth/verify` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/webauthn/register/options (apps/console/app/routes/api.passkey.tsx:34)
`apps/console/app/routes/api.passkey.tsx:34` calls `POST https://auth/webauthn/register/options` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/webauthn/register/options` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://auth/webauthn/register/verify (apps/console/app/routes/api.passkey.tsx:55)
`apps/console/app/routes/api.passkey.tsx:55` calls `POST https://auth/webauthn/register/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/webauthn/register/verify` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://billing/billing/checkout (apps/console/app/routes/billing.tsx:96)
`apps/console/app/routes/billing.tsx:96` calls `POST https://billing/billing/checkout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/billing/billing/checkout` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://billing/billing/portal (apps/console/app/routes/billing.tsx:113)
`apps/console/app/routes/billing.tsx:113` calls `POST https://billing/billing/portal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/billing/billing/portal` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://auth/orgs/${params.orgId}/saml/connection (apps/console/app/routes/saml-admin.tsx:89)
`apps/console/app/routes/saml-admin.tsx:89` calls `PUT https://auth/orgs/${params.orgId}/saml/connection` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/saml/connection` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://auth/orgs/${params.orgId}/sso/connection (apps/console/app/routes/sso-admin.tsx:90)
`apps/console/app/routes/sso-admin.tsx:90` calls `PUT https://auth/orgs/${params.orgId}/sso/connection` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth/orgs/<p>/sso/connection` If this points at an extern…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/console/app/routes/account-mfa.tsx:191
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/src/durable-objects/vault.ts:1034
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 — apps/api/src/middleware/auth.ts:22
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 — apps/api/src/routes/workspaces.ts:886
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 — apps/api/test/health.test.ts:8
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/test/machine.test.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 — apps/api/test/security.test.ts:19
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 — apps/api/test/workspace-ws.test.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 — apps/auth/test/routes.test.ts:23
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 — apps/console/app/lib/passkey.ts:15
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 — apps/console/app/lib/workspace.server.ts:15
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 — apps/console/app/routes/account-mfa.tsx:19
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 — apps/console/app/routes/api.passkey.tsx:34
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 — apps/console/app/routes/api.reveal-token.tsx:40
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 — apps/console/app/routes/assistant.tsx:32
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 — apps/console/app/routes/billing.tsx:36
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 — apps/console/app/routes/dashboard.audit.tsx:56
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 — apps/console/app/routes/dashboard.compare.tsx:69
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 — apps/console/app/routes/dashboard.notifications.tsx:56
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 — apps/console/app/routes/dashboard.tsx:84
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 — apps/console/app/routes/domains.tsx:70
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 — apps/console/app/routes/environment.tsx:87
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 — apps/console/app/routes/forgot-password.tsx:15
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 — apps/console/app/routes/home.tsx:30
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 — apps/console/app/routes/invite.tsx:31
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 — apps/console/app/routes/login.mfa.tsx:40
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 — apps/console/app/routes/login.tsx:49
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 — apps/console/app/routes/members.tsx:65
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 — apps/console/app/routes/oauth.callback.tsx: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 — apps/console/app/routes/oauth.start.tsx:17
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 — apps/console/app/routes/reset-password.tsx:22
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 — apps/console/app/routes/saml-admin.tsx:35
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 — apps/console/app/routes/saml.acs.tsx:27
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 — apps/console/app/routes/saml.start.tsx:15
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 — apps/console/app/routes/scim.tsx:28
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 — apps/console/app/routes/share.tsx:30
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 — apps/console/app/routes/share.view.tsx:21
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 — apps/console/app/routes/sso-admin.tsx:36
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 — apps/console/app/routes/sso.callback.tsx:28
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 — apps/console/app/routes/sso.start.tsx:16
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 — apps/console/app/routes/verify-email.tsx:19
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 — apps/console/workers/app.ts:28
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 — apps/delivery/test/delivery.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 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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/console/app/routes/account-mfa.tsx:191
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/console/app/routes/account-mfa.tsx:191 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/src/index.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/src/index.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in packages/auth/src/totp.ts:12
Found a known-risky pattern (weak_hash). Review and replace if possible.
packages/auth/src/totp.ts:12 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 40 placeholder/mock markers across 19 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 6 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 quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/api/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.
apps/api/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/audit/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.
apps/audit/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/auth/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.
apps/auth/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/console/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.
apps/console/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/delivery/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.
apps/delivery/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/notify/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.
apps/notify/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/www/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.
apps/www/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: edge/control-plane/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.
edge/control-plane/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ai/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.
packages/ai/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/auth/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.
packages/auth/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/cli/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.
packages/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/config-formats/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.
packages/config-formats/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/crypto/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.
packages/crypto/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/database/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.
packages/database/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/diff/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.
packages/diff/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/edge-protocol/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.
packages/edge-protocol/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/realtime/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.
packages/realtime/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/refs/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.
packages/refs/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/scim/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.
packages/scim/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/sdk/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.
packages/sdk/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/sso-saml/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.
packages/sso-saml/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/ui/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.
packages/ui/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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — edge/control-plane/src/index.ts:69
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 — packages/cli/src/bin.ts:4
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: GET
`packages/sso-saml/src/c14n.ts` declares `GET ` 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 /me
`apps/auth/src/index.ts` declares `GET /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 /mfa/status
`apps/auth/src/index.ts` declares `GET /mfa/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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /orgs/:orgId/saml/connection
`apps/auth/src/sso.ts` declares `GET /orgs/:orgId/saml/connection` 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 /orgs/:orgId/sso/connection
`apps/auth/src/sso.ts` declares `GET /orgs/:orgId/sso/connection` 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 /session
`apps/auth/src/index.ts` declares `GET /session` 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 /sessions
`apps/auth/src/index.ts` declares `GET /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 /v1/configs/:key
`apps/delivery/src/index.ts` declares `GET /v1/configs/:key` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/export
`apps/delivery/src/index.ts` declares `GET /v1/export` 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 /v1/flags/:key
`apps/delivery/src/index.ts` declares `GET /v1/flags/:key` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /internal/sso/provision
`apps/auth/src/index.ts` declares `POST /internal/sso/provision` 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 /mfa/recovery/authenticate
`apps/auth/src/index.ts` declares `POST /mfa/recovery/authenticate` 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 /mfa/recovery/regenerate
`apps/auth/src/index.ts` declares `POST /mfa/recovery/regenerate` 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 /mfa/totp/authenticate
`apps/auth/src/index.ts` declares `POST /mfa/totp/authenticate` 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 /mfa/totp/confirm
`apps/auth/src/index.ts` declares `POST /mfa/totp/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /mfa/totp/disable
`apps/auth/src/index.ts` declares `POST /mfa/totp/disable` 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 /mfa/totp/setup
`apps/auth/src/index.ts` declares `POST /mfa/totp/setup` 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 /oauth/:provider/callback
`apps/auth/src/index.ts` declares `POST /oauth/:provider/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: POST /oauth/:provider/start
`apps/auth/src/index.ts` declares `POST /oauth/:provider/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /orgs/:orgId/saml/acs
`apps/auth/src/sso.ts` declares `POST /orgs/:orgId/saml/acs` 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 /orgs/:orgId/saml/start
`apps/auth/src/sso.ts` declares `POST /orgs/:orgId/saml/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /orgs/:orgId/sso/callback
`apps/auth/src/sso.ts` declares `POST /orgs/:orgId/sso/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: POST /orgs/:orgId/sso/start
`apps/auth/src/sso.ts` declares `POST /orgs/:orgId/sso/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /password/change
`apps/auth/src/index.ts` declares `POST /password/change` 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 /password/forgot
`apps/auth/src/index.ts` declares `POST /password/forgot` 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 /password/reset
`apps/auth/src/index.ts` declares `POST /password/reset` 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 /reauth
`apps/auth/src/index.ts` declares `POST /reauth` 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 /sessions/:id/revoke
`apps/auth/src/index.ts` declares `POST /sessions/:id/revoke` 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 /sessions/revoke-all
`apps/auth/src/index.ts` declares `POST /sessions/revoke-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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sign-in/email
`apps/auth/src/index.ts` declares `POST /sign-in/email` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sign-out
`apps/auth/src/index.ts` declares `POST /sign-out` 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 /sign-up/email
`apps/auth/src/index.ts` declares `POST /sign-up/email` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /token
`apps/auth/src/index.ts` declares `POST /token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/batch
`apps/delivery/src/index.ts` declares `POST /v1/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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /verify-email
`apps/auth/src/index.ts` declares `POST /verify-email` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /verify-email/resend
`apps/auth/src/index.ts` declares `POST /verify-email/resend` 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 /webauthn/auth/options
`apps/auth/src/index.ts` declares `POST /webauthn/auth/options` 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 /webauthn/auth/verify
`apps/auth/src/index.ts` declares `POST /webauthn/auth/verify` 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 /webauthn/register/options
`apps/auth/src/index.ts` declares `POST /webauthn/register/options` 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 /webauthn/register/verify
`apps/auth/src/index.ts` declares `POST /webauthn/register/verify` 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 /orgs/:orgId/saml/connection
`apps/auth/src/sso.ts` declares `PUT /orgs/:orgId/saml/connection` 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 /orgs/:orgId/sso/connection
`apps/auth/src/sso.ts` declares `PUT /orgs/:orgId/sso/connection` 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: USE /api/v1/*
`apps/api/src/index.ts` declares `USE /api/v1/*` 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: USE /api/v1/workspaces/:workspaceId/*
`apps/api/src/index.ts` declares `USE /api/v1/workspaces/:workspaceId/*` 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: USE /mcp/:workspaceId
`apps/api/src/index.ts` declares `USE /mcp/:workspaceId` 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: USE /orgs/:orgId/*
`apps/auth/src/sso.ts` declares `USE /orgs/:orgId/*` 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: USE /orgs/:orgId/saml/*
`apps/auth/src/sso.ts` declares `USE /orgs/:orgId/saml/*` 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: USE /orgs/:orgId/sso/*
`apps/auth/src/sso.ts` declares `USE /orgs/:orgId/sso/*` 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: USE /scim/*
`apps/api/src/index.ts` declares `USE /scim/*` 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: USE /v1/*
`apps/delivery/src/index.ts` declares `USE /v1/*` 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/8a3f46df-c61e-49a2-955e-eab1a4efffa8/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8a3f46df-c61e-49a2-955e-eab1a4efffa8/

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.