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

Vedantdave66/Tandempay

https://github.com/Vedantdave66/Tandempay · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

250 raw signals (20 security + 230 graph)

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

Complete repo analysis

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

JSON
Combined
65.6
/100
Security checks
66
7 findings
System graph
66
100.0% cov · 203 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 100 Medium 6 Low 80 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 203 Crowd 0 Layer: Quality 29 Security 12 Software 10 Frontend 20 Hardware 1 Cicd 1 Api 137
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 65.6/100 with 100.0% coverage. It contains 2939 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 230 findings — concentrated in api (137), quality (31), software (26). Risk profile is high: 0 critical, 97 high, 9 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 188 of 210 actionable findings. 506 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 11 occurrences Foundry mined mock as real or placeholder: Vedantdave66/Tandempay
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…
11 occurrences
repo-level (11 hits)
critical Security checks security auth conf 0.78 10 occurrences Foundry mined security auth guardrail gaps: Vedantdave66/Tandempay
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…
10 occurrences
repo-level (10 hits)
high Security checks quality Practices conf 0.84 100 occurrences Foundry mined bad chains: Vedantdave66/Tandempay
Comment chain pattern product: bad_chains Repo: Vedantdave66/Tandempay Thread: Vedantdave66/Tandempay#93 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, sour…
100 occurrences
repo-level (100 hits)
high Security checks quality Quality conf 0.76 5 occurrences Foundry mined schema ui api mismatch: Vedantdave66/Tandempay
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: weak_supervision_needs_review Repo: V…
5 occurrences
repo-level (5 hits)
high Security checks quality Testing conf 0.78 3 occurrences Foundry mined test ci gap after feedback: Vedantdave66/Tandempay
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: weak_supervision_needs_…
3 occurrences
repo-level (3 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /bank-links/${id} (frontend/src/services/api.ts:374)
`frontend/src/services/api.ts:374` calls `DELETE /bank-links/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/bank-links/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId} (frontend/src/services/api.ts:166)
`frontend/src/services/api.ts:166` calls `DELETE /groups/${groupId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId} (mobile/src/services/api.ts:152)
`mobile/src/services/api.ts:152` calls `DELETE /groups/${groupId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId}/expenses/${expenseId} (frontend/src/services/api.ts:204)
`frontend/src/services/api.ts:204` calls `DELETE /groups/${groupId}/expenses/${expenseId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId}/expenses/${expenseId} (mobile/src/services/api.ts:190)
`mobile/src/services/api.ts:190` calls `DELETE /groups/${groupId}/expenses/${expenseId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId}/expenses/${expenseId}/reminder (frontend/src/services/api.ts:474)
`frontend/src/services/api.ts:474` calls `DELETE /groups/${groupId}/expenses/${expenseId}/reminder` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>/reminder` If this points at an exte…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId}/members/${userId} (frontend/src/services/api.ts:168)
`frontend/src/services/api.ts:168` calls `DELETE /groups/${groupId}/members/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/members/<p>` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /groups/${groupId}/members/${userId} (mobile/src/services/api.ts:154)
`mobile/src/services/api.ts:154` calls `DELETE /groups/${groupId}/members/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/members/<p>` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /recurring/${id} (frontend/src/services/api.ts:526)
`frontend/src/services/api.ts:526` calls `DELETE /recurring/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/recurring/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /recurring/${id} (mobile/src/services/api.ts:377)
`mobile/src/services/api.ts:377` calls `DELETE /recurring/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/recurring/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/me (frontend/src/services/api.ts:95)
`frontend/src/services/api.ts:95` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/me (mobile/src/services/api.ts:81)
`mobile/src/services/api.ts:81` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /bank-links (frontend/src/services/api.ts:373)
`frontend/src/services/api.ts:373` calls `GET /bank-links` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/bank-links` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /friends/requests/pending (frontend/src/services/api.ts:349)
`frontend/src/services/api.ts:349` calls `GET /friends/requests/pending` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests/pending` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /friends/requests/pending (mobile/src/services/api.ts:255)
`mobile/src/services/api.ts:255` calls `GET /friends/requests/pending` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests/pending` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups (mobile/src/services/api.ts:136)
`mobile/src/services/api.ts:136` calls `GET /groups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${groupId}/balances (frontend/src/services/api.ts:240)
`frontend/src/services/api.ts:240` calls `GET /groups/${groupId}/balances` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/balances` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${groupId}/balances (mobile/src/services/api.ts:219)
`mobile/src/services/api.ts:219` calls `GET /groups/${groupId}/balances` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/balances` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${groupId}/expenses (mobile/src/services/api.ts:183)
`mobile/src/services/api.ts:183` calls `GET /groups/${groupId}/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${groupId}/expenses/${expenseId}/reminder (frontend/src/services/api.ts:472)
`frontend/src/services/api.ts:472` calls `GET /groups/${groupId}/expenses/${expenseId}/reminder` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>/reminder` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${groupId}/settlements (frontend/src/services/api.ts:241)
`frontend/src/services/api.ts:241` calls `GET /groups/${groupId}/settlements` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/settlements` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${groupId}/settlements (mobile/src/services/api.ts:220)
`mobile/src/services/api.ts:220` calls `GET /groups/${groupId}/settlements` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/settlements` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${id} (frontend/src/services/api.ts:152)
`frontend/src/services/api.ts:152` calls `GET /groups/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/${id} (mobile/src/services/api.ts:137)
`mobile/src/services/api.ts:137` calls `GET /groups/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /groups/join/${token} (frontend/src/services/api.ts:164)
`frontend/src/services/api.ts:164` calls `GET /groups/join/${token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/join/<p>` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /me/friends (mobile/src/services/api.ts:261)
`mobile/src/services/api.ts:261` calls `GET /me/friends` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/friends` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /me/payments (mobile/src/services/api.ts:284)
`mobile/src/services/api.ts:284` calls `GET /me/payments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/payments` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /notifications (mobile/src/services/api.ts:314)
`mobile/src/services/api.ts:314` calls `GET /notifications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /notifications/unread-count (frontend/src/services/api.ts:294)
`frontend/src/services/api.ts:294` calls `GET /notifications/unread-count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/unread-count` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /notifications/unread-count (mobile/src/services/api.ts:315)
`mobile/src/services/api.ts:315` calls `GET /notifications/unread-count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/unread-count` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /recurring (mobile/src/services/api.ts:365)
`mobile/src/services/api.ts:365` calls `GET /recurring` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/recurring` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /stripe/status (frontend/src/services/api.ts:389)
`frontend/src/services/api.ts:389` calls `GET /stripe/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/stripe/status` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /users/search?query=${encodeURIComponent(query)} (frontend/src/services/api.ts:322)
`frontend/src/services/api.ts:322` calls `GET /users/search?query=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/search` If this points at an external API, prefix it with…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /wallet/balance (frontend/src/services/api.ts:406)
`frontend/src/services/api.ts:406` calls `GET /wallet/balance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/wallet/balance` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /wallet/balance (mobile/src/services/api.ts:335)
`mobile/src/services/api.ts:335` calls `GET /wallet/balance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/wallet/balance` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /wallet/transactions (mobile/src/services/api.ts:336)
`mobile/src/services/api.ts:336` calls `GET /wallet/transactions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/wallet/transactions` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /auth/me (frontend/src/services/api.ts:107)
`frontend/src/services/api.ts:107` calls `PATCH /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /auth/me (mobile/src/services/api.ts:89)
`mobile/src/services/api.ts:89` calls `PATCH /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /recurring/${id} (frontend/src/services/api.ts:521)
`frontend/src/services/api.ts:521` calls `PATCH /recurring/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/recurring/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /users/me/character (frontend/src/services/api.ts:324)
`frontend/src/services/api.ts:324` calls `PATCH /users/me/character` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/me/character` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/login (frontend/src/services/api.ts:91)
`frontend/src/services/api.ts:91` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/login (mobile/src/services/api.ts:77)
`mobile/src/services/api.ts:77` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/register (frontend/src/services/api.ts:86)
`frontend/src/services/api.ts:86` calls `POST /auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/register` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/register (mobile/src/services/api.ts:72)
`mobile/src/services/api.ts:72` calls `POST /auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/register` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/reset-password (frontend/src/services/api.ts:102)
`frontend/src/services/api.ts:102` calls `POST /auth/reset-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/reset-password` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /bank-links (frontend/src/services/api.ts:369)
`frontend/src/services/api.ts:369` calls `POST /bank-links` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/bank-links` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /friends/requests (frontend/src/services/api.ts:345)
`frontend/src/services/api.ts:345` calls `POST /friends/requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /friends/requests (mobile/src/services/api.ts:250)
`mobile/src/services/api.ts:250` calls `POST /friends/requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups (frontend/src/services/api.ts:150)
`frontend/src/services/api.ts:150` calls `POST /groups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups (mobile/src/services/api.ts:135)
`mobile/src/services/api.ts:135` calls `POST /groups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/expenses (frontend/src/services/api.ts:193)
`frontend/src/services/api.ts:193` calls `POST /groups/${groupId}/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/expenses (mobile/src/services/api.ts:179)
`mobile/src/services/api.ts:179` calls `POST /groups/${groupId}/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/expenses/${expenseId}/reminder (frontend/src/services/api.ts:467)
`frontend/src/services/api.ts:467` calls `POST /groups/${groupId}/expenses/${expenseId}/reminder` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>/reminder` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/invite/generate (mobile/src/services/api.ts:148)
`mobile/src/services/api.ts:148` calls `POST /groups/${groupId}/invite/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/invite/generate` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/join (frontend/src/services/api.ts:159)
`frontend/src/services/api.ts:159` calls `POST /groups/${groupId}/join` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/join` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/join (mobile/src/services/api.ts:144)
`mobile/src/services/api.ts:144` calls `POST /groups/${groupId}/join` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/join` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/members (frontend/src/services/api.ts:154)
`frontend/src/services/api.ts:154` calls `POST /groups/${groupId}/members` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/members` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/members (mobile/src/services/api.ts:139)
`mobile/src/services/api.ts:139` calls `POST /groups/${groupId}/members` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/members` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/settlement-records (frontend/src/services/api.ts:267)
`frontend/src/services/api.ts:267` calls `POST /groups/${groupId}/settlement-records` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/settlement-records` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/${groupId}/settlement-records (mobile/src/services/api.ts:289)
`mobile/src/services/api.ts:289` calls `POST /groups/${groupId}/settlement-records` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/settlement-records` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /groups/join/${token} (mobile/src/services/api.ts:150)
`mobile/src/services/api.ts:150` calls `POST /groups/join/${token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/join/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /payments/create (frontend/src/services/api.ts:440)
`frontend/src/services/api.ts:440` calls `POST /payments/create` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/payments/create` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /payments/create (mobile/src/services/api.ts:483)
`mobile/src/services/api.ts:483` calls `POST /payments/create` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/payments/create` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /plaid/create-link-token (frontend/src/services/api.ts:378)
`frontend/src/services/api.ts:378` calls `POST /plaid/create-link-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/plaid/create-link-token` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /plaid/set-access-token (frontend/src/services/api.ts:380)
`frontend/src/services/api.ts:380` calls `POST /plaid/set-access-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/plaid/set-access-token` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /receipts/parse (mobile/src/services/api.ts:402)
`mobile/src/services/api.ts:402` calls `POST /receipts/parse` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/receipts/parse` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /recurring (frontend/src/services/api.ts:516)
`frontend/src/services/api.ts:516` calls `POST /recurring` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/recurring` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /recurring (mobile/src/services/api.ts:373)
`mobile/src/services/api.ts:373` calls `POST /recurring` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/recurring` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /smart-split (mobile/src/services/api.ts:432)
`mobile/src/services/api.ts:432` calls `POST /smart-split` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/smart-split` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /stripe/cleanup (frontend/src/services/api.ts:392)
`frontend/src/services/api.ts:392` calls `POST /stripe/cleanup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/stripe/cleanup` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /stripe/onboard?return_path=${encodeURIComponent(returnPath)} (frontend/src/services/api.ts:388)
`frontend/src/services/api.ts:388` calls `POST /stripe/onboard?return_path=${encodeURIComponent(returnPath)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/stripe/onboard` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /stripe/reconcile/${paymentId} (frontend/src/services/api.ts:391)
`frontend/src/services/api.ts:391` calls `POST /stripe/reconcile/${paymentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/stripe/reconcile/<p>` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /stripe/reconcile/${paymentId} (frontend/src/services/api.ts:451)
`frontend/src/services/api.ts:451` calls `POST /stripe/reconcile/${paymentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/stripe/reconcile/<p>` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /wallet/add-funds (mobile/src/services/api.ts:338)
`mobile/src/services/api.ts:338` calls `POST /wallet/add-funds` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/wallet/add-funds` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /wallet/withdraw (mobile/src/services/api.ts:343)
`mobile/src/services/api.ts:343` calls `POST /wallet/withdraw` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/wallet/withdraw` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /friends/requests/${id}/accept (frontend/src/services/api.ts:350)
`frontend/src/services/api.ts:350` calls `PUT /friends/requests/${id}/accept` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests/<p>/accept` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /friends/requests/${id}/decline (frontend/src/services/api.ts:351)
`frontend/src/services/api.ts:351` calls `PUT /friends/requests/${id}/decline` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests/<p>/decline` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /friends/requests/${requestId}/accept (mobile/src/services/api.ts:257)
`mobile/src/services/api.ts:257` calls `PUT /friends/requests/${requestId}/accept` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests/<p>/accept` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /friends/requests/${requestId}/decline (mobile/src/services/api.ts:259)
`mobile/src/services/api.ts:259` calls `PUT /friends/requests/${requestId}/decline` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/friends/requests/<p>/decline` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /groups/${groupId}/expenses/${expenseId} (frontend/src/services/api.ts:199)
`frontend/src/services/api.ts:199` calls `PUT /groups/${groupId}/expenses/${expenseId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /groups/${groupId}/expenses/${expenseId} (mobile/src/services/api.ts:185)
`mobile/src/services/api.ts:185` calls `PUT /groups/${groupId}/expenses/${expenseId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/expenses/<p>` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /groups/${groupId}/settlement-records/${settlementId}/status (frontend/src/services/api.ts:273)
`frontend/src/services/api.ts:273` calls `PUT /groups/${groupId}/settlement-records/${settlementId}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/settlement-records/<p>/status` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /groups/${groupId}/settlement-records/${settlementId}/status (mobile/src/services/api.ts:294)
`mobile/src/services/api.ts:294` calls `PUT /groups/${groupId}/settlement-records/${settlementId}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>/settlement-records/<p>/status` If this poi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /notifications/${id}/read (frontend/src/services/api.ts:295)
`frontend/src/services/api.ts:295` calls `PUT /notifications/${id}/read` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/<p>/read` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /notifications/${id}/read (mobile/src/services/api.ts:317)
`mobile/src/services/api.ts:317` calls `PUT /notifications/${id}/read` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/<p>/read` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /notifications/read-all (frontend/src/services/api.ts:296)
`frontend/src/services/api.ts:296` calls `PUT /notifications/read-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/read-all` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /notifications/read-all (mobile/src/services/api.ts:319)
`mobile/src/services/api.ts:319` calls `PUT /notifications/read-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/read-all` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `admin_diagnose_hashes` without auth dependency — backend/app/routes/auth.py:465
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/auth.py:465 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `admin_reset_all_passwords` without auth dependency — backend/app/routes/auth.py:371
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/auth.py:371 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cleanup_payments` without auth dependency — backend/app/routes/stripe_routes.py:459
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/stripe_routes.py:459 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `forgot_password` without auth dependency — backend/app/routes/auth.py:276
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/auth.py:276 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `interac_inbound` without auth dependency — backend/app/routes/interac_routes.py:44
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/interac_routes.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reconcile_payment` without auth dependency — backend/app/routes/stripe_routes.py:388
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/stripe_routes.py:388 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reconcile_stuck_payments` without auth dependency — backend/app/services/reconciliation.py:19
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/services/reconciliation.py:19 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset_password` without auth dependency — backend/app/routes/auth.py:324
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/auth.py:324 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — backend/app/routes/stripe_routes.py:130
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/stripe_routes.py:130 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_nudge_job` without auth dependency — backend/app/routes/debug_routes.py:11
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routes/debug_routes.py:11 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 54 occurrences Foundry mined assumption checks: Vedantdave66/Tandempay
Comment chain pattern product: assumption_checks Repo: Vedantdave66/Tandempay Thread: Vedantdave66/Tandempay#208 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_gra…
54 occurrences
repo-level (54 hits)
medium Security checks quality Practices conf 0.70 93 occurrences Foundry mined unresolved feedback: Vedantdave66/Tandempay
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…
93 occurrences
repo-level (93 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 quality Integrity conf 1.00 6 occurrences Frontend route `/reset-password` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/context/AuthContext.tsx:38
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/context/AuthContext.tsx:38 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 70 placeholder/mock markers across 29 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 Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AWS_LAMBDA_FUNCTION_NAME`, `DEV`, `GEMINI_API_KEY`, `MODE`, `PROD`, `RESEND_FROM_EMAIL`, `STRIPE_SECRET_KEY`, `VERCEL` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 49 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 cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/backend-ci.yml:36, 39 (2 hits)
.github/workflows/frontend-ci.yml:23, 26 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
19 tests / 185 src (ratio 0.10).
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/routes/expenses.py:list_expenses, backend/app/routes/settlements.py:list_settlements This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're se…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/app/schemas.py:validate_password_complexity, backend/app/schemas.py:validate_password_complexity, backend/app/schemas.py:validate_password_complexity This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://j…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: backend/app/routes/notifications.py:list_notifications, backend/app/routes/wallet.py:get_transactions, backend/app/routes/me.py:get_my_payments, backend/app/routes/me.py:get_my_friends This is *the* AI-coder failure mode (4× more duplication in vibe-…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: assert_conservation_of_money
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ledger.py:84
low System graph software Dead code conf 1.00 9 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
9 files, 9 locations
backend/alembic/versions/20260513_add_audit_logs.py:70
backend/alembic/versions/20260522_add_recurring_expenses.py:71
backend/alembic/versions/20260524_payment_retry_partial_index.py:49
backend/alembic/versions/20260525_add_password_reset_tokens.py:32
backend/alembic/versions/20260525_check_constraints_and_status_enums.py:92
backend/alembic/versions/20260527_add_character_columns.py:22
backend/alembic/versions/20260612_add_push_token_to_users.py:20
backend/alembic/versions/7af805ecb0e7_add_interac_email_logs_table.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: format
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/main.py:63
low System graph software Dead code conf 1.00 Possibly dead Python function: lock_users_sorted
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ledger.py:158
low System graph software Dead code conf 1.00 Possibly dead Python function: pre_validate_balance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ledger.py:41
low System graph software Dead code conf 1.00 Possibly dead Python function: process_due_reminders
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/reminder_scheduler.py:23
low System graph software Dead code conf 1.00 Possibly dead Python function: require_pro
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/dependencies/subscription.py:7
low System graph software Dead code conf 1.00 Possibly dead Python function: run_payment_reconciliation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/payment_reconciliation.py:15
low System graph software Dead code conf 1.00 9 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
9 files, 9 locations
backend/alembic/versions/20260513_add_audit_logs.py:30
backend/alembic/versions/20260522_add_recurring_expenses.py:35
backend/alembic/versions/20260524_payment_retry_partial_index.py:30
backend/alembic/versions/20260525_add_password_reset_tokens.py:16
backend/alembic/versions/20260525_check_constraints_and_status_enums.py:47
backend/alembic/versions/20260527_add_character_columns.py:16
backend/alembic/versions/20260612_add_push_token_to_users.py:16
backend/alembic/versions/7af805ecb0e7_add_interac_email_logs_table.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_post_commit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ledger.py:123
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 — frontend/src/components/StripePaymentModal.tsx:66
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/main.tsx:40
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 — mobile/src/context/AuthContext.tsx:41
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 — mobile/src/screens/GroupsScreen.tsx:46
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 — mobile/src/screens/SmartSplitScreen.tsx:296
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 — mobile/src/screens/SubscriptionScreen.tsx:47
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 — mobile/src/services/api.ts:18
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 /{expense_id}
`backend/app/routes/expenses.py` declares `DELETE /{expense_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 /{group_id}
`backend/app/routes/groups.py` declares `DELETE /{group_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 /{group_id}/invite
`backend/app/routes/groups.py` declares `DELETE /{group_id}/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{group_id}/members/{user_id}
`backend/app/routes/groups.py` declares `DELETE /{group_id}/members/{user_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 /
`backend/app/main.py` 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 /api/health
`backend/app/main.py` declares `GET /api/health` 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 /balance
`backend/app/routes/wallet.py` declares `GET /balance` 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 /csv
`backend/app/routes/export_routes.py` declares `GET /csv` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /friends
`backend/app/routes/me.py` declares `GET /friends` 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 /groups/{group_id}/requests
`backend/app/routes/requests.py` declares `GET /groups/{group_id}/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 or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /join/{token}
`backend/app/routes/groups.py` declares `GET /join/{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: GET /me
`backend/app/routes/auth.py` 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 /payments
`backend/app/routes/me.py` declares `GET /payments` 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 /pdf
`backend/app/routes/export_routes.py` declares `GET /pdf` 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 /search
`backend/app/routes/users.py` declares `GET /search` 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 /transactions
`backend/app/routes/wallet.py` declares `GET /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 code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /unread-count
`backend/app/routes/notifications.py` declares `GET /unread-count` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{group_id}
`backend/app/routes/groups.py` declares `GET /{group_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 /{group_id}/audit-log
`backend/app/routes/audit_log.py` declares `GET /{group_id}/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /me
`backend/app/routes/auth.py` declares `PATCH /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: PATCH /me/character
`backend/app/routes/users.py` declares `PATCH /me/character` 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 /
`backend/app/routes/expenses.py` declares `POST /` 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 /add-funds
`backend/app/routes/wallet.py` declares `POST /add-funds` 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 /admin/diagnose-hashes
`backend/app/routes/auth.py` declares `POST /admin/diagnose-hashes` 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 /admin/reset-all-passwords
`backend/app/routes/auth.py` declares `POST /admin/reset-all-passwords` 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 /checkout
`backend/app/routes/subscription_routes.py` declares `POST /checkout` 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 /cleanup
`backend/app/routes/stripe_routes.py` declares `POST /cleanup` 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 /create
`backend/app/routes/payments.py` declares `POST /create` 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 /create-link-token
`backend/app/routes/plaid_routes.py` declares `POST /create-link-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 /forgot-password
`backend/app/routes/auth.py` declares `POST /forgot-password` 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 /inbound
`backend/app/routes/interac_routes.py` declares `POST /inbound` 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 /join/{token}
`backend/app/routes/groups.py` declares `POST /join/{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 /login
`backend/app/routes/auth.py` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /logout
`backend/app/routes/auth.py` declares `POST /logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /onboard
`backend/app/routes/stripe_routes.py` declares `POST /onboard` 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 /portal
`backend/app/routes/subscription_routes.py` declares `POST /portal` 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 /reconcile/{payment_id}
`backend/app/routes/stripe_routes.py` declares `POST /reconcile/{payment_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: POST /register
`backend/app/routes/auth.py` declares `POST /register` 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 /reset-password
`backend/app/routes/auth.py` declares `POST /reset-password` 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 /set-access-token
`backend/app/routes/plaid_routes.py` declares `POST /set-access-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 /voice
`backend/app/routes/smart_split.py` declares `POST /voice` 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 /webhook
`backend/app/routes/stripe_routes.py` declares `POST /webhook` 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 /withdraw
`backend/app/routes/wallet.py` declares `POST /withdraw` 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 /{group_id}/invite/generate
`backend/app/routes/groups.py` declares `POST /{group_id}/invite/generate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{group_id}/join
`backend/app/routes/groups.py` declares `POST /{group_id}/join` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{group_id}/members
`backend/app/routes/groups.py` declares `POST /{group_id}/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /read-all
`backend/app/routes/notifications.py` declares `PUT /read-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{expense_id}
`backend/app/routes/expenses.py` declares `PUT /{expense_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: PUT /{notification_id}/read
`backend/app/routes/notifications.py` declares `PUT /{notification_id}/read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{settlement_id}/status
`backend/app/routes/settlements.py` declares `PUT /{settlement_id}/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 quality Complexity conf 1.00 Very large file: mobile/src/components/CanvasModeView.tsx (1427 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: mobile/src/screens/GroupDetailScreen.tsx (1025 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: mobile/src/screens/SmartSplitScreen.tsx (1530 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/16426285-f88b-4abd-909e-291d94e5a5a8/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/16426285-f88b-4abd-909e-291d94e5a5a8/

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.