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

Reshigan/Heirloom

https://github.com/Reshigan/Heirloom · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

334 raw signals (0 security + 334 graph)

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

Complete repo analysis

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

JSON
Combined
47.6
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 268 findings
Critical
10
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 10 High 61 Medium 56 Low 100 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 268 Crowd 0 Layer: Frontend 29 Hardware 5 Security 26 Cicd 2 Quality 96 Api 110
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 47.6/100 with 100.0% coverage. It contains 3477 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 334 findings — concentrated in quality (146), api (110), frontend (29). Risk profile is high: 13 critical, 61 high, 108 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in cloudflare/worker/src/services/pushSender.ts:53
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
cloudflare/worker/src/services/pushSender.ts:53 Private key in repo
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in cloudflare/frontend/src/pages/Signup.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 91, 92
cloudflare/frontend/src/pages/Signup.tsx:91, 92 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in mobile/src/screens/LoginScreen.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
mobile/src/screens/LoginScreen.tsx:40
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in mobile/src/screens/SignupScreen.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 46, 48, 52
mobile/src/screens/SignupScreen.tsx:46, 48, 52 (3 hits)
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: cloudflare/frontend/.env.production
`cloudflare/frontend/.env.production` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_VAPID_PUBLIC_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
cloudflare/frontend/.env.production ConfigEnv fileRuntime env
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.stripe.com/v1/customers/${stripeCustomerId} (cloudflare/worker/src/crons/scheduled-deletion.ts:37)
`cloudflare/worker/src/crons/scheduled-deletion.ts:37` calls `DELETE https://api.stripe.com/v1/customers/${stripeCustomerId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/customers/<p>` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.stripe.com/v1/customers/${stripeCustomerId} (cloudflare/worker/src/routes/settings.ts:919)
`cloudflare/worker/src/routes/settings.ts:919` calls `DELETE https://api.stripe.com/v1/customers/${stripeCustomerId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/customers/<p>` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.stripe.com/v1/accounts/${influencer.stripe_account_id} (cloudflare/worker/src/routes/influencers.ts:625)
`cloudflare/worker/src/routes/influencers.ts:625` calls `GET https://api.stripe.com/v1/accounts/${influencer.stripe_account_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/accounts/<p>` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.stripe.com/v1/customers?email=${encodeURIComponent(user.email as string)}&limit=1 (cloudflare/worker/src/routes/billing.ts:784)
`cloudflare/worker/src/routes/billing.ts:784` calls `GET https://api.stripe.com/v1/customers?email=${encodeURIComponent(user.email as string)}&limit=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.strip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://app.ayrshare.com/api/analytics/post?id=${id} (marketing/automation/src/metrics.ts:31)
`marketing/automation/src/metrics.ts:31` calls `GET https://app.ayrshare.com/api/analytics/post?id=${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/app.ayrshare.com/api/analytics/post` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://bsky.social/xrpc/com.atproto.repo.getRecord?repo=${s.did}&collection=app.bsky.actor.profile&rkey=self (marketing/automation/scripts/social-launch.ts:71)
`marketing/automation/scripts/social-launch.ts:71` calls `GET https://bsky.social/xrpc/com.atproto.repo.getRecord?repo=${s.did}&collection=app.bsky.actor.profile&rkey=self` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matchin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://bsky.social/xrpc/com.atproto.repo.getRecord?repo=${sess.did}&collection=app.bsky.actor.profile&rkey=self (marketing/automation/src/run.ts:337)
`marketing/automation/src/run.ts:337` calls `GET https://bsky.social/xrpc/com.atproto.repo.getRecord?repo=${sess.did}&collection=app.bsky.actor.profile&rkey=self` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://heirloom.blue/icons/icon-512.png (marketing/automation/src/run.ts:322)
`marketing/automation/src/run.ts:322` calls `GET https://heirloom.blue/icons/icon-512.png` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/heirloom.blue/icons/icon-512.png` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: HEAD https://cloudflare-ipfs.com/ipfs/${p.snapshot_cid} (cloudflare/worker/src/services/archive.ts:247)
`cloudflare/worker/src/services/archive.ts:247` calls `HEAD https://cloudflare-ipfs.com/ipfs/${p.snapshot_cid}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/cloudflare-ipfs.com/ipfs/<p>` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudflare.com/client/v4/accounts/${account}/ai/run/${CLOUDFLARE_MODEL} (marketing/automation/src/generate.ts:153)
`marketing/automation/src/generate.ts:153` calls `POST https://api.cloudflare.com/client/v4/accounts/${account}/ai/run/${CLOUDFLARE_MODEL}` 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/cl…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.linkedin.com/v2/ugcPosts (marketing/automation/src/post.ts:300)
`marketing/automation/src/post.ts:300` calls `POST https://api.linkedin.com/v2/ugcPosts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.linkedin.com/v2/ugcposts` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.pinata.cloud/pinning/pinJSONToIPFS (cloudflare/worker/src/services/archive.ts:169)
`cloudflare/worker/src/services/archive.ts:169` calls `POST https://api.pinata.cloud/pinning/pinJSONToIPFS` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.pinata.cloud/pinning/pinjsontoipfs` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.pinterest.com/v5/pins (marketing/automation/scripts/social-launch.ts:238)
`marketing/automation/scripts/social-launch.ts:238` calls `POST https://api.pinterest.com/v5/pins` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.pinterest.com/v5/pins` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.pinterest.com/v5/pins (marketing/automation/src/post.ts:321)
`marketing/automation/src/post.ts:321` calls `POST https://api.pinterest.com/v5/pins` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.pinterest.com/v5/pins` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (cloudflare/worker/src/utils/email.ts:174)
`cloudflare/worker/src/utils/email.ts:174` calls `POST https://api.resend.com/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.resend.com/emails` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/account_links (cloudflare/worker/src/routes/influencers.ts:530)
`cloudflare/worker/src/routes/influencers.ts:530` calls `POST https://api.stripe.com/v1/account_links` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/account_links` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/account_links (cloudflare/worker/src/routes/influencers.ts:582)
`cloudflare/worker/src/routes/influencers.ts:582` calls `POST https://api.stripe.com/v1/account_links` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/account_links` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/accounts (cloudflare/worker/src/routes/influencers.ts:495)
`cloudflare/worker/src/routes/influencers.ts:495` calls `POST https://api.stripe.com/v1/accounts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/accounts` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/billing_portal/sessions (cloudflare/worker/src/routes/billing.ts:796)
`cloudflare/worker/src/routes/billing.ts:796` calls `POST https://api.stripe.com/v1/billing_portal/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/billing_portal/sessions` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/checkout/sessions (cloudflare/worker/src/routes/billing.ts:658)
`cloudflare/worker/src/routes/billing.ts:658` calls `POST https://api.stripe.com/v1/checkout/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/checkout/sessions` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/checkout/sessions (cloudflare/worker/src/routes/books.ts:181)
`cloudflare/worker/src/routes/books.ts:181` calls `POST https://api.stripe.com/v1/checkout/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/checkout/sessions` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/checkout/sessions (cloudflare/worker/src/routes/founders.ts:73)
`cloudflare/worker/src/routes/founders.ts:73` calls `POST https://api.stripe.com/v1/checkout/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/checkout/sessions` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/checkout/sessions (cloudflare/worker/src/routes/gift-vouchers.ts:230)
`cloudflare/worker/src/routes/gift-vouchers.ts:230` calls `POST https://api.stripe.com/v1/checkout/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/checkout/sessions` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/checkout/sessions (cloudflare/worker/src/routes/partners.ts:558)
`cloudflare/worker/src/routes/partners.ts:558` calls `POST https://api.stripe.com/v1/checkout/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/checkout/sessions` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/subscriptions/${sub.stripe_subscription_id} (cloudflare/worker/src/routes/billing.ts:702)
`cloudflare/worker/src/routes/billing.ts:702` calls `POST https://api.stripe.com/v1/subscriptions/${sub.stripe_subscription_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/subscriptions/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/subscriptions/${sub.stripe_subscription_id} (cloudflare/worker/src/routes/billing.ts:736)
`cloudflare/worker/src/routes/billing.ts:736` calls `POST https://api.stripe.com/v1/subscriptions/${sub.stripe_subscription_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/subscriptions/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/subscriptions?customer=${stripeCustomerId}&status=active&limit=5 (cloudflare/worker/src/routes/settings.ts:897)
`cloudflare/worker/src/routes/settings.ts:897` calls `POST https://api.stripe.com/v1/subscriptions?customer=${stripeCustomerId}&status=active&limit=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1/transfers (cloudflare/worker/src/jobs/adoption-jobs.ts:1497)
`cloudflare/worker/src/jobs/adoption-jobs.ts:1497` calls `POST https://api.stripe.com/v1/transfers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/transfers` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.web3.storage/upload (cloudflare/worker/src/services/archive.ts:152)
`cloudflare/worker/src/services/archive.ts:152` calls `POST https://api.web3.storage/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.web3.storage/upload` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.createRecord (marketing/automation/scripts/bluesky-promo.ts:111)
`marketing/automation/scripts/bluesky-promo.ts:111` calls `POST https://bsky.social/xrpc/com.atproto.repo.createRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.creater…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.createRecord (marketing/automation/scripts/social-launch.ts:125)
`marketing/automation/scripts/social-launch.ts:125` calls `POST https://bsky.social/xrpc/com.atproto.repo.createRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.creater…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.createRecord (marketing/automation/src/post.ts:461)
`marketing/automation/src/post.ts:461` calls `POST https://bsky.social/xrpc/com.atproto.repo.createRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.createrecord` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.deleteRecord (marketing/automation/src/run.ts:390)
`marketing/automation/src/run.ts:390` calls `POST https://bsky.social/xrpc/com.atproto.repo.deleteRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.deleterecord` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.putRecord (marketing/automation/scripts/social-launch.ts:75)
`marketing/automation/scripts/social-launch.ts:75` calls `POST https://bsky.social/xrpc/com.atproto.repo.putRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.putrecord` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.putRecord (marketing/automation/src/run.ts:352)
`marketing/automation/src/run.ts:352` calls `POST https://bsky.social/xrpc/com.atproto.repo.putRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.putrecord` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.putRecord (scripts/update-social-profiles.mjs:61)
`scripts/update-social-profiles.mjs:61` calls `POST https://bsky.social/xrpc/com.atproto.repo.putRecord` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.putrecord` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob (marketing/automation/scripts/bluesky-promo.ts:56)
`marketing/automation/scripts/bluesky-promo.ts:56` calls `POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.uploadblob…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob (marketing/automation/scripts/social-launch.ts:56)
`marketing/automation/scripts/social-launch.ts:56` calls `POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.uploadblob…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob (marketing/automation/src/post.ts:351)
`marketing/automation/src/post.ts:351` calls `POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.uploadblob` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob (marketing/automation/src/run.ts:327)
`marketing/automation/src/run.ts:327` calls `POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.uploadblob` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob (scripts/update-social-profiles.mjs:41)
`scripts/update-social-profiles.mjs:41` calls `POST https://bsky.social/xrpc/com.atproto.repo.uploadBlob` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.repo.uploadblob` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (marketing/automation/scripts/bluesky-promo.ts:39)
`marketing/automation/scripts/bluesky-promo.ts:39` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.cre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (marketing/automation/scripts/social-launch.ts:41)
`marketing/automation/scripts/social-launch.ts:41` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.cre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (marketing/automation/src/engage.ts:76)
`marketing/automation/src/engage.ts:76` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.createsession`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (marketing/automation/src/post.ts:380)
`marketing/automation/src/post.ts:380` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.createsession` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (marketing/automation/src/run.ts:307)
`marketing/automation/src/run.ts:307` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.createsession` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (marketing/automation/src/run.ts:367)
`marketing/automation/src/run.ts:367` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.createsession` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://bsky.social/xrpc/com.atproto.server.createSession (scripts/update-social-profiles.mjs:30)
`scripts/update-social-profiles.mjs:30` calls `POST https://bsky.social/xrpc/com.atproto.server.createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/bsky.social/xrpc/com.atproto.server.createsession`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${igUserId}/media (marketing/automation/scripts/social-launch.ts:206)
`marketing/automation/scripts/social-launch.ts:206` calls `POST https://graph.facebook.com/v21.0/${igUserId}/media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/media` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${igUserId}/media (marketing/automation/src/post.ts:263)
`marketing/automation/src/post.ts:263` calls `POST https://graph.facebook.com/v21.0/${igUserId}/media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/media` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${igUserId}/media_publish (marketing/automation/scripts/social-launch.ts:210)
`marketing/automation/scripts/social-launch.ts:210` calls `POST https://graph.facebook.com/v21.0/${igUserId}/media_publish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/media_pu…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${igUserId}/media_publish (marketing/automation/src/post.ts:272)
`marketing/automation/src/post.ts:272` calls `POST https://graph.facebook.com/v21.0/${igUserId}/media_publish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/media_publish` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${j.id}/comments (marketing/automation/scripts/social-launch.ts:176)
`marketing/automation/scripts/social-launch.ts:176` calls `POST https://graph.facebook.com/v21.0/${j.id}/comments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/comments` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${json.id}/comments (marketing/automation/src/post.ts:236)
`marketing/automation/src/post.ts:236` calls `POST https://graph.facebook.com/v21.0/${json.id}/comments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/comments` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${pageId}/photos (marketing/automation/scripts/social-launch.ts:170)
`marketing/automation/scripts/social-launch.ts:170` calls `POST https://graph.facebook.com/v21.0/${pageId}/photos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/photos` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${pageId}/photos (scripts/update-social-profiles.mjs:102)
`scripts/update-social-profiles.mjs:102` calls `POST https://graph.facebook.com/v21.0/${pageId}/photos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/photos` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v21.0/${pageId}/picture (marketing/automation/scripts/social-launch.ts:144)
`marketing/automation/scripts/social-launch.ts:144` calls `POST https://graph.facebook.com/v21.0/${pageId}/picture` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v21.0/<p>/picture` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (cloudflare/worker/src/services/pushSender.ts:179)
`cloudflare/worker/src/services/pushSender.ts:179` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://open.tiktokapis.com/v2/research/user/info/?fields=bio_description (cloudflare/worker/src/jobs/adoption-jobs.ts:840)
`cloudflare/worker/src/jobs/adoption-jobs.ts:840` calls `POST https://open.tiktokapis.com/v2/research/user/info/?fields=bio_description` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/open.tiktokapis.com/v2/r…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://open.tiktokapis.com/v2/research/video/query/?fields=username,follower_count,region_code,bio_description (cloudflare/worker/src/jobs/adoption-jobs.ts:658)
`cloudflare/worker/src/jobs/adoption-jobs.ts:658` calls `POST https://open.tiktokapis.com/v2/research/video/query/?fields=username,follower_count,region_code,bio_description` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for match…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in cloudflare/worker-configuration.d.ts:2997
Found a known-risky pattern (exec_used). Review and replace if possible.
cloudflare/worker-configuration.d.ts:2997 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/src/routes/support.ts:489
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 — backend/src/services/tinyllm.service.ts:67
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 — cloudflare/frontend/public/sw.js:123
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 — cloudflare/frontend/src/loom/components/ComposerChrome.tsx:76
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 — cloudflare/frontend/src/pages/AdminDashboard.tsx:148
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 — cloudflare/frontend/src/pages/Record.tsx:252
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 — cloudflare/frontend/src/services/encryptionService.ts:99
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 — cloudflare/worker-configuration.d.ts:336
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 — cloudflare/worker/src/__tests__/auth.worker.test.ts: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 — cloudflare/worker/src/__tests__/gift-vouchers.worker.test.ts:24
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — cloudflare/worker/src/__tests__/health.worker.test.ts:18
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 — cloudflare/worker/src/crons/social-posting.ts:58
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 — cloudflare/worker/src/index.ts:1637
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 — cloudflare/worker/src/jobs/adoption-jobs.ts:746
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 — cloudflare/worker/src/routes/admin.ts:45
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 — cloudflare/worker/src/routes/billing.ts:658
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 — cloudflare/worker/src/routes/influencers.ts:530
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 — cloudflare/worker/src/routes/partners.ts:558
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 — cloudflare/worker/src/routes/q4-features.ts:225
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 — cloudflare/worker/src/routes/settings.ts:904
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 — cloudflare/worker/src/routes/social-import.ts:390
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 — cloudflare/worker/src/services/archive.ts:152
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 — cloudflare/worker/src/services/book.ts:104
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 — cloudflare/worker/src/services/mailbox-bounce-detector.ts:95
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 — cloudflare/worker/src/services/pushSender.ts:105
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 — cloudflare/worker/src/services/webPushSender.ts:186
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 — marketing/automation/scripts/bluesky-promo.ts:39
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 — marketing/automation/scripts/social-launch.ts:41
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 — marketing/automation/src/generate.ts:153
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — marketing/automation/src/metrics.ts: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 — marketing/automation/src/post.ts:300
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 — marketing/automation/src/run.ts:322
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 — scripts/update-social-profiles.mjs: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 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 license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: cloudflare/frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 51 occurrences Frontend route `/daily` has no Link/navigate to it — cloudflare/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.
51 occurrences
repo-level (51 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/social-autopost.yml
.github/workflows/social-batch.yml
.github/workflows/social-promo.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in cloudflare/frontend/scripts/live-seeded-shots.mjs:199
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
cloudflare/frontend/scripts/live-seeded-shots.mjs:199 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in cloudflare/frontend/scripts/mock-authed-shots.mjs:24
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
cloudflare/frontend/scripts/mock-authed-shots.mjs:24 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in cloudflare/worker/src/routes/voice.ts:250
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
cloudflare/worker/src/routes/voice.ts:250 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in cloudflare/frontend/public/offline-boot.js:34
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
cloudflare/frontend/public/offline-boot.js:34 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in cloudflare/frontend/src/loom/components/ClothWeave.tsx:396
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
cloudflare/frontend/src/loom/components/ClothWeave.tsx:396 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in cloudflare/frontend/src/loom/components/CosmicLoom.tsx:336
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
cloudflare/frontend/src/loom/components/CosmicLoom.tsx:336 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in cloudflare/frontend/scripts/audit-pages.mjs:25
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
cloudflare/frontend/scripts/audit-pages.mjs:25 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in cloudflare/frontend/scripts/live-seeded-shots.mjs:189
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
cloudflare/frontend/scripts/live-seeded-shots.mjs:189 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in cloudflare/frontend/scripts/mock-authed-shots.mjs:10
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
cloudflare/frontend/scripts/mock-authed-shots.mjs:10 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in cloudflare/frontend/src/pages/AdminLogin.tsx:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
cloudflare/frontend/src/pages/AdminLogin.tsx:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in cloudflare/frontend/src/pages/GiftReceive.tsx:67
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
cloudflare/frontend/src/pages/GiftReceive.tsx:67 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in cloudflare/frontend/src/services/api.ts:12
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
cloudflare/frontend/src/services/api.ts:12 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/generate-social-video.js:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/generate-social-video.js:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/generate-tiktok.mjs:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/generate-tiktok.mjs:23 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 219 placeholder/mock markers across 69 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
18 test file(s) for 328 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 32 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_JWT_SECRET`, `AUDIT_AUTH`, `AYRSHARE_API_KEY`, `BASE`, `BASE_URL`, `CI`, `CLOUDFLARE_AI_MODEL`, `DRY_RUN` + 24 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 255 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
cloudflare/frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 12 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, 12 locations
.github/workflows/pr-checks.yml:13, 56, 59, 77, 80, 101, 104, 125, +1 more (9 hits)
.github/workflows/d1-backup.yml:20, 23, 69 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — cloudflare/frontend/src/pages/QandA.tsx:321
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph 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 quality Integrity conf 1.00 Old/deprecated-named symbol `certIssuerDNLegacy` in cloudflare/worker-configuration.d.ts:10446
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `isGoldLegacy` in cloudflare/frontend/src/pages/GoldLegacyRedeem.tsx:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `isGoldLegacy` in cloudflare/worker/src/routes/auth.ts:68
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `isLegacy` in cloudflare/worker/src/routes/gift-vouchers.ts:186
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `refetchGoldLegacy` in cloudflare/frontend/src/pages/AdminDashboard.tsx:170
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `safeOld` in cloudflare/worker/src/routes/settings.ts:378
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/routes/notifications.ts:194
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/routes/support.ts:486
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/utils/seed.ts:39
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 — cloudflare/frontend/e2e/04-pwa-install.spec.ts:109
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 — cloudflare/frontend/e2e/regression.spec.ts:312
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 — cloudflare/worker-configuration.d.ts:203
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 — cloudflare/worker/sim/lifetime.test.ts:314
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 — cloudflare/worker/src/crons/scheduled-deletion.ts:87
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 — cloudflare/worker/src/index.ts:930
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 — cloudflare/worker/src/jobs/adoption-jobs.ts:2328
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 — cloudflare/worker/src/routes/admin.ts:2273
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 — cloudflare/worker/src/routes/ai.ts:226
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 — cloudflare/worker/src/services/mailbox-bounce-detector.ts:325
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 — cloudflare/worker/src/services/pushSender.ts:251
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 — marketing/automation/scripts/bluesky-promo.ts:72
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 — marketing/automation/scripts/social-launch.ts:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — marketing/automation/src/batch.ts:96
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 — marketing/automation/src/engage.ts:111
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 — marketing/automation/src/post.ts:228
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 — marketing/automation/src/run.ts:92
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 — marketing/automation/src/seo.ts:207
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/scripts/generate-icons.js:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-all-videos.js:51
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 — scripts/generate-content-json.js:882
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 — scripts/generate-social-assets.js:122
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 — scripts/generate-social-video.js:118
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 /auth/me
`mobile/src/services/api.ts` declares `GET /auth/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /billing/limits
`cloudflare/frontend/src/services/api.ts` declares `GET /billing/limits` 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 /billing/pricing
`cloudflare/frontend/src/services/api.ts` declares `GET /billing/pricing` 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 /billing/subscription
`cloudflare/frontend/src/services/api.ts` declares `GET /billing/subscription` 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 /capsules
`cloudflare/frontend/src/services/api.ts` declares `GET /capsules` 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 /engagement/family-feed
`cloudflare/frontend/src/services/api.ts` declares `GET /engagement/family-feed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /engagement/legacy-score
`cloudflare/frontend/src/services/api.ts` declares `GET /engagement/legacy-score` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /family
`mobile/src/services/api.ts` declares `GET /family` 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 /legacy-plan
`cloudflare/frontend/src/pages/LegacyPlan.tsx` declares `GET /legacy-plan` 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 /legacy/score
`mobile/src/services/api.ts` declares `GET /legacy/score` 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 /letters
`mobile/src/services/api.ts` declares `GET /letters` 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 /letters/awaiting-me
`cloudflare/frontend/src/services/api.ts` declares `GET /letters/awaiting-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 /letters/received
`cloudflare/frontend/src/services/api.ts` declares `GET /letters/received` 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 /life-events
`cloudflare/frontend/src/pages/LifeEvents.tsx` declares `GET /life-events` 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 /memories
`mobile/src/services/api.ts` declares `GET /memories` 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 /memories/map
`cloudflare/frontend/src/services/api.ts` declares `GET /memories/map` 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 /memories/received
`cloudflare/frontend/src/services/api.ts` declares `GET /memories/received` 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 /memories/stats/summary
`cloudflare/frontend/src/services/api.ts` declares `GET /memories/stats/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /memory-cards/on-this-day
`cloudflare/frontend/src/services/api.ts` declares `GET /memory-cards/on-this-day` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /story-artifacts
`cloudflare/frontend/src/pages/StoryArtifact.tsx` declares `GET /story-artifacts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /voice
`mobile/src/services/api.ts` declares `GET /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: GET /voice/prompts/list
`cloudflare/frontend/src/services/api.ts` declares `GET /voice/prompts/list` 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 /voice/stats
`cloudflare/frontend/src/services/api.ts` declares `GET /voice/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /billing/currency
`cloudflare/frontend/src/services/api.ts` declares `PATCH /billing/currency` 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 /legacy-plan/share
`cloudflare/frontend/src/pages/LegacyPlan.tsx` declares `PATCH /legacy-plan/share` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/forgot-password
`cloudflare/frontend/src/services/api.ts` declares `POST /auth/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 /auth/login
`mobile/src/services/api.ts` declares `POST /auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/logout
`cloudflare/frontend/src/services/api.ts` declares `POST /auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/refresh
`cloudflare/frontend/src/services/api.ts` declares `POST /auth/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/register
`cloudflare/frontend/src/services/api.ts` declares `POST /auth/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 /auth/reset-password
`cloudflare/frontend/src/services/api.ts` declares `POST /auth/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 /auth/signup
`mobile/src/services/api.ts` declares `POST /auth/signup` 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 /billing/cancel
`cloudflare/frontend/src/services/api.ts` declares `POST /billing/cancel` 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 /billing/checkout
`cloudflare/frontend/src/services/api.ts` declares `POST /billing/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 /billing/portal
`cloudflare/frontend/src/services/api.ts` declares `POST /billing/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 /capsules
`cloudflare/frontend/src/services/api.ts` declares `POST /capsules` 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 /family
`mobile/src/services/api.ts` declares `POST /family` 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 /gift-vouchers/redeem
`cloudflare/frontend/src/pages/GiftRedeem.tsx` declares `POST /gift-vouchers/redeem` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /gifts/send
`cloudflare/frontend/src/services/api.ts` declares `POST /gifts/send` 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 /legacy-plan/items
`cloudflare/frontend/src/pages/LegacyPlan.tsx` declares `POST /legacy-plan/items` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /letters
`mobile/src/services/api.ts` declares `POST /letters` 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 /letters/ai-suggest
`cloudflare/frontend/src/services/api.ts` declares `POST /letters/ai-suggest` 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 /life-events
`cloudflare/frontend/src/pages/LifeEvents.tsx` declares `POST /life-events` 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 /memories
`mobile/src/services/api.ts` declares `POST /memories` 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 /memories/upload-url
`cloudflare/frontend/src/services/api.ts` declares `POST /memories/upload-url` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /push/web-subscribe
`cloudflare/frontend/src/lib/webPush.ts` declares `POST /push/web-subscribe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /story-artifacts
`cloudflare/frontend/src/pages/StoryArtifact.tsx` declares `POST /story-artifacts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /voice
`mobile/src/services/api.ts` 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 /voice/upload-url
`cloudflare/frontend/src/services/api.ts` declares `POST /voice/upload-url` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /auth/profile
`mobile/src/services/api.ts` declares `PUT /auth/profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: cloudflare/frontend/src/pages/AdminDashboard.tsx (2101 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/frontend/src/pages/Compose.tsx (1658 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker-configuration.d.ts (12856 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker/src/email-templates.ts (1268 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker/src/index.ts (1700 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker/src/jobs/adoption-jobs.ts (2344 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker/src/routes/admin.ts (2730 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker/src/routes/billing.ts (1284 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cloudflare/worker/src/routes/export.ts (1675 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/40bc01d8-04f6-41b6-83f2-94df5efb3143/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/40bc01d8-04f6-41b6-83f2-94df5efb3143/

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.