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

steveyeow/Feynman

https://github.com/steveyeow/Feynman · scanned 2026-06-16 00:22 UTC (2 months, 2 weeks ago)

247 raw signals (74 security + 173 graph)

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

Complete repo analysis

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

JSON
Combined
64.6
/100
Security checks
65
8 findings
System graph
65
100.0% cov · 164 findings
Critical
3
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 6 Medium 27 Low 83 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 164 Crowd 0 Layer: Quality 81 Security 18 Software 14 Frontend 9 Api 50
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 64.6/100 with 100.0% coverage. It contains 2474 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 173 findings — concentrated in quality (82), api (50), security (18). Risk profile is high: 2 critical, 3 high, 24 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical Security checks quality Practices conf 0.82 3 occurrences Foundry mined mock as real or placeholder: steveyeow/Feynman
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
3 occurrences
repo-level (3 hits)
critical Security checks security auth conf 0.78 7 occurrences Foundry mined security auth guardrail gaps: steveyeow/Feynman
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
7 occurrences
repo-level (7 hits)
high Security checks quality Practices conf 0.84 83 occurrences Foundry mined bad chains: steveyeow/Feynman
Comment chain pattern product: bad_chains Repo: steveyeow/Feynman Thread: steveyeow/Feynman#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_ha…
83 occurrences
repo-level (83 hits)
high Security checks quality Quality conf 0.76 8 occurrences Foundry mined schema ui api mismatch: steveyeow/Feynman
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: assumption_check Repo: steveyeow/Feyn…
8 occurrences
repo-level (8 hits)
high Security checks quality Testing conf 0.78 5 occurrences Foundry mined test ci gap after feedback: steveyeow/Feynman
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
5 occurrences
repo-level (5 hits)
high System graph security auth conf 1.00 FastAPI POST `create_checkout_session` without auth dependency — app/pro/stripe.py:30
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/pro/stripe.py:30 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_portal_session` without auth dependency — app/pro/stripe.py:140
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/pro/stripe.py:140 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — app/pro/stripe.py:63
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/pro/stripe.py:63 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 76 occurrences Foundry mined assumption checks: steveyeow/Feynman
Comment chain pattern product: assumption_checks Repo: steveyeow/Feynman Thread: steveyeow/Feynman#61 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph…
76 occurrences
repo-level (76 hits)
medium Security checks quality maintenance conf 0.70 54 occurrences Foundry mined blueprint gap alignment: steveyeow/Feynman
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
54 occurrences
repo-level (54 hits)
medium Security checks quality Practices conf 0.70 83 occurrences Foundry mined unresolved feedback: steveyeow/Feynman
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
83 occurrences
repo-level (83 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/app/a/[id]/page.tsx:236
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/app/layout.tsx:126
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/components/chat/markdown.ts:5
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/components/chat/MessageList.tsx:238
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/components/chat/MindConsent.tsx:33
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/components/chat/useMentionAutocomplete.tsx:202
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/components/reader/Reader.tsx:564
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/components/seo/JsonLd.tsx:9
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in app/main.py:157
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
app/main.py:157 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/app/a/[id]/page.tsx:236
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/app/a/[id]/page.tsx:236 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/app/layout.tsx:126
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/app/layout.tsx:126 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/components/chat/MessageList.tsx:238
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/components/chat/MessageList.tsx:238 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/components/chat/MindConsent.tsx:33
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/components/chat/MindConsent.tsx:33 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/components/chat/useMentionAutocomplete.tsx:202
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/components/chat/useMentionAutocomplete.tsx:202 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/components/reader/Reader.tsx:564
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/components/reader/Reader.tsx:564 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/components/seo/JsonLd.tsx:9
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/components/seo/JsonLd.tsx:9 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app/static/app.js:238
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app/static/app.js:238 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in demo-ai-book-writer.html:407
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
demo-ai-book-writer.html:407 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web/components/landing/LandingPage.tsx:375
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web/components/landing/LandingPage.tsx:375 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in app/static/app.js:3375
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
app/static/app.js:3375 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in app/static/app.js:2540
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
app/static/app.js:2540 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 52 placeholder/mock markers across 15 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
10 test file(s) for 169 source file(s) (ratio 0.06). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 51 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_USER_IDS`, `ALERT_EMAIL`, `ALERT_FROM`, `ANTHROPIC_API_KEY`, `ANTHROPIC_BASE_URL`, `ANTHROPIC_CHAT_MODEL`, `API_BASE`, `APP_URL` + 43 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 115 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: app/main.py:api_chat_session_share, app/main.py:api_chat This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: app/core/skills.py:is_available, app/core/skills.py:is_available, app/core/skills.py:is_available This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're s…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: app/core/providers.py:has_key, app/core/providers.py:has_key, app/core/providers.py:has_key, app/core/providers.py:has_key This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: app/core/skills.py:execute, app/core/skills.py:execute, app/core/skills.py:execute, app/core/skills.py:execute This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `mind_similarities_v1` in app/main.py:5448
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 `rest_v1` in app/core/sources.py:15
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 `rest_v1` in app/core/sources_wikidata.py:59
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: ensure_catalog_agents
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/db.py:1834
low System graph software Dead code conf 1.00 Possibly dead Python function: expand_symposiums
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/debates.py:419
low System graph software Dead code conf 1.00 Possibly dead Python function: find_user_by_stripe_customer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/db.py:4043
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/text_utils.py:25
low System graph software Dead code conf 1.00 Possibly dead Python function: is_llm_enabled
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/qa.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: is_mind_essay_enabled
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/qa.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: regenerate_debate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/debates.py:390
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_agent_id_by_slug
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/db.py:1246
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_mind_id_by_slug
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/db.py:1258
low System graph software Dead code conf 1.00 Possibly dead Python function: run_debate_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/debates.py:225
low System graph software Dead code conf 1.00 Possibly dead Python function: suggest_minds_for_book
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/minds.py:949
low System graph software Dead code conf 1.00 Possibly dead Python function: update_agent_slug
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/db.py:1295
low System graph software Dead code conf 1.00 Possibly dead Python function: update_mind_slug
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/db.py:2101
low System graph software Dead code conf 1.00 Possibly dead Python function: write_full_book
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/ai_writer.py:223
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 — app/static/app.js:3174
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 /
`app/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/llm-referrals
`app/main.py` declares `GET /api/admin/llm-referrals` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/moderation-queue/count
`app/main.py` declares `GET /api/admin/moderation-queue/count` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/chat-sessions/{session_id}/public-status
`app/main.py` declares `GET /api/chat-sessions/{session_id}/public-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/discover
`app/main.py` declares `GET /api/cron/discover` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/egress-watch
`app/main.py` declares `GET /api/cron/egress-watch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/embed-minds
`app/main.py` declares `GET /api/cron/embed-minds` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/generate-symposiums
`app/main.py` declares `GET /api/cron/generate-symposiums` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/indexnow
`app/main.py` declares `GET /api/cron/indexnow` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/mind-qa
`app/main.py` declares `GET /api/cron/mind-qa` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/prestore-overviews
`app/main.py` declares `GET /api/cron/prestore-overviews` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/reset-embeddings
`app/main.py` declares `GET /api/cron/reset-embeddings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/seed-minds
`app/main.py` declares `GET /api/cron/seed-minds` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/voice-minds
`app/main.py` declares `GET /api/cron/voice-minds` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/debug/embedding-status
`app/main.py` declares `GET /api/debug/embedding-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`app/main.py` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/minds/{mind_id}/q/{slug}
`app/main.py` declares `GET /api/minds/{mind_id}/q/{slug}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/minds/{mind_id}/questions
`app/main.py` declares `GET /api/minds/{mind_id}/questions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/og-image/{agent_id}
`app/main.py` declares `GET /api/og-image/{agent_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 /api/pro/config
`app/main.py` declares `GET /api/pro/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/pro/subscription
`app/main.py` declares `GET /api/pro/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 /api/public-answers/{answer_id}
`app/main.py` declares `GET /api/public-answers/{answer_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 /api/public/book/{agent_id}/read
`app/main.py` declares `GET /api/public/book/{agent_id}/read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/topics
`app/main.py` declares `GET /api/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 /book/{agent_id}
`app/main.py` declares `GET /book/{agent_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 /book/{agent_id}/discussions
`app/main.py` declares `GET /book/{agent_id}/discussions` 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 /book/{agent_id}/insights
`app/main.py` declares `GET /book/{agent_id}/insights` 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 /book/{agent_id}/og.png
`app/main.py` declares `GET /book/{agent_id}/og.png` 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 /book/{agent_id}/q/{question_slug}
`app/main.py` declares `GET /book/{agent_id}/q/{question_slug}` 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 /discussions/{session_id}
`app/main.py` declares `GET /discussions/{session_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 /llms-full.txt
`app/main.py` declares `GET /llms-full.txt` 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 /llms.txt
`app/main.py` declares `GET /llms.txt` 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 /mind/{mind_id}
`app/main.py` declares `GET /mind/{mind_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 /mind/{mind_id}/dialogues
`app/main.py` declares `GET /mind/{mind_id}/dialogues` 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 /mind/{mind_id}/discussions
`app/main.py` declares `GET /mind/{mind_id}/discussions` 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 /mind/{mind_id}/og.png
`app/main.py` declares `GET /mind/{mind_id}/og.png` 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 /mind/{mind_id}/on/{topic_slug}
`app/main.py` declares `GET /mind/{mind_id}/on/{topic_slug}` 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 /privacy
`app/main.py` declares `GET /privacy` 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 /share/{agent_id}
`app/main.py` declares `GET /share/{agent_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 /share/{agent_id}/og.png
`app/main.py` declares `GET /share/{agent_id}/og.png` 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 /sitemap
`app/main.py` declares `GET /sitemap` 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 /terms
`app/main.py` declares `GET /terms` 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 /topic/{slug}
`app/main.py` declares `GET /topic/{slug}` 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 /api/admin/chat-sessions/{session_id}/approve
`app/main.py` declares `POST /api/admin/chat-sessions/{session_id}/approve` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/chat-sessions/{session_id}/reject
`app/main.py` declares `POST /api/admin/chat-sessions/{session_id}/reject` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/chat-sessions/{session_id}/messages/{message_index}/share
`app/main.py` declares `POST /api/chat-sessions/{session_id}/messages/{message_index}/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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/discover
`app/main.py` declares `POST /api/discover` 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 /api/public-answers/{answer_id}/withdraw
`app/main.py` declares `POST /api/public-answers/{answer_id}/withdraw` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/public-discussions/{session_id}/report
`app/main.py` declares `POST /api/public-discussions/{session_id}/report` 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 /api/search-book
`app/main.py` declares `POST /api/search-book` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: app/core/db.py (4325 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/core/minds.py (1321 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/core/seo.py (1468 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/main.py (5742 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/static/app.js (7959 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_seo_pages.py (2284 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/components/chat/ChatView.tsx (1325 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/components/landing/LandingPage.tsx (1386 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/2cdfa986-3cee-4dd2-8fae-c278cf253110/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2cdfa986-3cee-4dd2-8fae-c278cf253110/

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.