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

andrehz4/setlists-pj-ev

https://github.com/andrehz4/setlists-pj-ev · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

158 raw signals (0 security + 158 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -28.0 (diff) · 151 actionable findings from 1 signal source. 7 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 89 of 151 actionable findings. 158 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.

high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/candidates (mock-ig/web/src/api.js:98)
`mock-ig/web/src/api.js:98` calls `GET /_mock/candidates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/candidates` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/control (mock-ig/web/src/api.js:44)
`mock-ig/web/src/api.js:44` calls `GET /_mock/control` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/control` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/curation (mock-ig/web/src/api.js:75)
`mock-ig/web/src/api.js:75` calls `GET /_mock/curation` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/curation` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/curation-runs (mock-ig/web/src/api.js:82)
`mock-ig/web/src/api.js:82` calls `GET /_mock/curation-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/curation-runs` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/feed (mock-ig/web/src/api.js:5)
`mock-ig/web/src/api.js:5` calls `GET /_mock/feed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/feed` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/reels (mock-ig/web/src/api.js:17)
`mock-ig/web/src/api.js:17` calls `GET /_mock/reels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/reels` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/runs (mock-ig/web/src/api.js:113)
`mock-ig/web/src/api.js:113` calls `GET /_mock/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/runs` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/stories (mock-ig/web/src/api.js:11)
`mock-ig/web/src/api.js:11` calls `GET /_mock/stories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/stories` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /_mock/usage (mock-ig/web/src/api.js:24)
`mock-ig/web/src/api.js:24` calls `GET /_mock/usage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/usage` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/curation-run (mock-ig/web/src/api.js:90)
`mock-ig/web/src/api.js:90` calls `POST /_mock/curation-run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/curation-run` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/delete (mock-ig/web/src/api.js:37)
`mock-ig/web/src/api.js:37` calls `POST /_mock/delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/delete` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/fail (mock-ig/web/src/api.js:52)
`mock-ig/web/src/api.js:52` calls `POST /_mock/fail` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/fail` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/preview (mock-ig/web/src/api.js:105)
`mock-ig/web/src/api.js:105` calls `POST /_mock/preview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/preview` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/reset (mock-ig/web/src/api.js:30)
`mock-ig/web/src/api.js:30` calls `POST /_mock/reset` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/reset` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/run (mock-ig/web/src/api.js:121)
`mock-ig/web/src/api.js:121` calls `POST /_mock/run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/run` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /_mock/sync (mock-ig/web/src/api.js:60)
`mock-ig/web/src/api.js:60` calls `POST /_mock/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/_mock/sync` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.github.com/gists (cloudflare-worker/news-merge-dispatch.js:107)
`cloudflare-worker/news-merge-dispatch.js:107` calls `POST https://api.github.com/gists` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/gists` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/dispatches (cloudflare-worker/news-merge-dispatch.js:138)
`cloudflare-worker/news-merge-dispatch.js:138` calls `POST https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/dispatches` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>/dispa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${TG_TOKEN}/sendMessage (scripts/publish/auto-merge-routine.mjs:198)
`scripts/publish/auto-merge-routine.mjs:198` calls `POST https://api.telegram.org/bot${TG_TOKEN}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (scripts/news/community-fetch.mjs:376)
`scripts/news/community-fetch.mjs:376` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (scripts/publish/run-publish-reel.mjs:218)
`scripts/publish/run-publish-reel.mjs:218` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (scripts/publish/run-publish-story.mjs:241)
`scripts/publish/run-publish-story.mjs:241` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (scripts/publish/run-publish.mjs:439)
`scripts/publish/run-publish.mjs:439` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points at an ex…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `create_bot_topic` without auth dependency — backend/app/routes/forum.py:173
`@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/forum.py:173 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'exec_used' in mock-ig/runs.mjs:13
Found a known-risky pattern (exec_used). Review and replace if possible.
mock-ig/runs.mjs:13 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — cloudflare-worker/news-merge-dispatch.js:54
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 — media/lib/smplr/index.mjs:51
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 — mock-ig/mock.test.mjs:25
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 — mock-ig/web/src/api.js:5
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 — mock-ig/web/src/components/CurationLab.jsx:12
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/publish/detect-deleted.test.mjs:35
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/publish/recover-publish.test.mjs:43
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/publish/reel.test.mjs:228
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/publish/telegram-bot.mjs: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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
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 cicd CI/CD security conf 1.00 7 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
7 files, 7 locations
.github/workflows/community.yml
.github/workflows/forum-seed.yml
.github/workflows/news-merge.yml
.github/workflows/news.yml
.github/workflows/publish-instagram.yml
.github/workflows/publish-reel.yml
.github/workflows/publish-story.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in cloudflare-worker/reddit-proxy.js:63
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
cloudflare-worker/reddit-proxy.js:63 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in mock-ig/server.mjs:50
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mock-ig/server.mjs:50 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in forum-profile.html:357
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
forum-profile.html:357 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in forum-topic.html:591
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
forum-topic.html:591 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in forum.html:843
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
forum.html:843 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in purify.min.js:2
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
purify.min.js:2 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in auth-callback.html:82
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
auth-callback.html:82 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in mock-ig/curation-runs.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
mock-ig/curation-runs.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in mock-ig/runs.mjs:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
mock-ig/runs.mjs:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in mock-ig/server.mjs:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
mock-ig/server.mjs:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/news/reddit-rss-fetch.mjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/news/reddit-rss-fetch.mjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish/auto-merge-routine.mjs:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish/auto-merge-routine.mjs:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish/reel-video.mjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish/reel-video.mjs:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish/run-publish-reel.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish/run-publish-reel.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish/run-publish-story.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish/run-publish-story.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish/run-publish.mjs:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish/run-publish.mjs:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish/story-video.mjs:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish/story-video.mjs:34 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 110 placeholder/mock markers across 28 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 284 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 18
backend/Dockerfile:2, 18 (2 hits)
containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — mock-ig/web/src/components/FailPanel.jsx:35
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — mock-ig/web/src/components/PostModal.jsx:24
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — mock-ig/web/src/components/StoryViewer.jsx:37
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 Tests conf 1.00 Low test-to-source ratio
18 tests / 151 src (ratio 0.12).
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 `postedOld` in scripts/publish/queue-select.test.mjs:168
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 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/core/logging.py:12
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /comments/{comment_id}
`backend/app/routes/feed.py` declares `DELETE /comments/{comment_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 /posts/{post_id}
`backend/app/routes/forum.py` declares `DELETE /posts/{post_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 /topics/{topic_id}
`backend/app/routes/forum.py` declares `DELETE /topics/{topic_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 /auth/google/callback
`backend/app/routes/auth.py` declares `GET /auth/google/callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/google/login
`backend/app/routes/auth.py` declares `GET /auth/google/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: GET /auth/me
`backend/app/routes/auth.py` 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 /posts
`backend/app/routes/feed.py` declares `GET /posts` 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 /posts/{post_id}
`backend/app/routes/feed.py` declares `GET /posts/{post_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 /topics
`backend/app/routes/forum.py` declares `GET /topics` 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 /topics/{topic_id}
`backend/app/routes/forum.py` declares `GET /topics/{topic_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 /users/{user_id}
`backend/app/routes/forum.py` declares `GET /users/{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 /users/{user_id}/badges
`backend/app/routes/forum.py` declares `GET /users/{user_id}/badges` 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 /users/me
`backend/app/routes/forum.py` declares `PATCH /users/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: POST /bot/topics
`backend/app/routes/forum.py` declares `POST /bot/topics` 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 /posts
`backend/app/routes/feed.py` declares `POST /posts` 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 /posts/{post_id}/comments
`backend/app/routes/feed.py` declares `POST /posts/{post_id}/comments` 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 /posts/{post_id}/likes
`backend/app/routes/feed.py` declares `POST /posts/{post_id}/likes` 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 /reactions
`backend/app/routes/forum.py` declares `POST /reactions` 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 /reports
`backend/app/routes/forum.py` declares `POST /reports` 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 /topics
`backend/app/routes/forum.py` declares `POST /topics` 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 /topics/{topic_id}/posts
`backend/app/routes/forum.py` declares `POST /topics/{topic_id}/posts` 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: media/lib/smplr/index.mjs (3840 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/261fb65f-96be-4c73-bace-9636e66de50d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/261fb65f-96be-4c73-bace-9636e66de50d/

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.