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.

ZhangShiCheng3D/MathVerse

https://github.com/ZhangShiCheng3D/MathVerse · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

140 raw signals (17 security + 123 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 56.7/100 with 100.0% coverage. It contains 1051 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 123 findings — concentrated in api (95), quality (12), security (7). Risk profile is high: 0 critical, 49 high, 9 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 126 of 130 actionable findings. 155 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 4 occurrences Foundry mined mock as real or placeholder: ZhangShiCheng3D/MathVerse
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…
4 occurrences
repo-level (4 hits)
critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: ZhangShiCheng3D/MathVerse
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…
high Security checks quality Practices conf 0.84 3 occurrences Foundry mined bad chains: ZhangShiCheng3D/MathVerse
Comment chain pattern product: bad_chains Repo: ZhangShiCheng3D/MathVerse Thread: ZhangShiCheng3D/MathVerse#15 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, sou…
3 occurrences
repo-level (3 hits)
high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: ZhangShiCheng3D/MathVerse
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: weak_supervisio…
high Security checks quality Quality conf 0.76 Foundry mined schema ui api mismatch: ZhangShiCheng3D/MathVerse
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: supported_by_verification_signal Repo…
high Security checks quality Testing conf 0.78 8 occurrences Foundry mined test ci gap after feedback: ZhangShiCheng3D/MathVerse
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…
8 occurrences
repo-level (8 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/book/${encodeURIComponent(id)} (mathverse-miniapp/src/stores/book.ts:94)
`mathverse-miniapp/src/stores/book.ts:94` calls `DELETE /api/book/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/book/<p>` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/kb/${encodeURIComponent(name)} (mathverse-miniapp/src/stores/kb.ts:110)
`mathverse-miniapp/src/stores/kb.ts:110` calls `DELETE /api/kb/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/kb/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/notebook/${encodeURIComponent(id)} (mathverse-miniapp/src/stores/notebook.ts:50)
`mathverse-miniapp/src/stores/notebook.ts:50` calls `DELETE /api/notebook/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notebook/<p>` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/activity/${encodeURIComponent(id)} (mathverse-miniapp/src/stores/activity.ts:50)
`mathverse-miniapp/src/stores/activity.ts:50` calls `GET /api/activity/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/activity/<p>` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/activity/recent (mathverse-miniapp/src/stores/activity.ts:40)
`mathverse-miniapp/src/stores/activity.ts:40` calls `GET /api/activity/recent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/activity/recent` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/me (mathverse-miniapp/src/stores/user.ts:78)
`mathverse-miniapp/src/stores/user.ts:78` calls `GET /api/auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/book/${encodeURIComponent(id)} (mathverse-miniapp/src/stores/book.ts:80)
`mathverse-miniapp/src/stores/book.ts:80` calls `GET /api/book/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/book/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/book/list (mathverse-miniapp/src/stores/book.ts:46)
`mathverse-miniapp/src/stores/book.ts:46` calls `GET /api/book/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/book/list` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/kb/list (mathverse-miniapp/src/stores/kb.ts:90)
`mathverse-miniapp/src/stores/kb.ts:90` calls `GET /api/kb/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/kb/list` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/learn/kg/kaoyan (mathverse-miniapp/src/pages/score/index.tsx:30)
`mathverse-miniapp/src/pages/score/index.tsx:30` calls `GET /api/learn/kg/kaoyan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/learn/kg/kaoyan` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/mistakes/review-today (mathverse-miniapp/src/pages/me/index.tsx:38)
`mathverse-miniapp/src/pages/me/index.tsx:38` calls `GET /api/me/mistakes/review-today` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/mistakes/review-today` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/mistakes?${qs} (mathverse-miniapp/src/pages/mistakes/index.tsx:57)
`mathverse-miniapp/src/pages/mistakes/index.tsx:57` calls `GET /api/me/mistakes?${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/mistakes` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/plan/today (mathverse-miniapp/src/pages/plan/index.tsx:19)
`mathverse-miniapp/src/pages/plan/index.tsx:19` calls `GET /api/me/plan/today` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/plan/today` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/progress (mathverse-miniapp/src/pages/me/index.tsx:37)
`mathverse-miniapp/src/pages/me/index.tsx:37` calls `GET /api/me/progress` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/progress` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/score/estimate?exam_mode=${mode} (mathverse-miniapp/src/pages/score/index.tsx:41)
`mathverse-miniapp/src/pages/score/index.tsx:41` calls `GET /api/me/score/estimate?exam_mode=${mode}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/score/estimate` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/memory/doc/${layer}/${encodeURIComponent(key)} (mathverse-miniapp/src/stores/memory.ts:46)
`mathverse-miniapp/src/stores/memory.ts:46` calls `GET /api/memory/doc/${layer}/${encodeURIComponent(key)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/memory/doc/<p>/<p>` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/memory/overview (mathverse-miniapp/src/stores/memory.ts:33)
`mathverse-miniapp/src/stores/memory.ts:33` calls `GET /api/memory/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/memory/overview` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/notebook/list (mathverse-miniapp/src/stores/notebook.ts:30)
`mathverse-miniapp/src/stores/notebook.ts:30` calls `GET /api/notebook/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notebook/list` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/pay/plans (mathverse-miniapp/src/pages/membership/index.tsx:26)
`mathverse-miniapp/src/pages/membership/index.tsx:26` calls `GET /api/pay/plans` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pay/plans` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/pay/subscription (mathverse-miniapp/src/pages/membership/index.tsx:23)
`mathverse-miniapp/src/pages/membership/index.tsx:23` calls `GET /api/pay/subscription` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pay/subscription` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tutor/capabilities (mathverse-miniapp/src/stores/tutor.ts:150)
`mathverse-miniapp/src/stores/tutor.ts:150` calls `GET /api/tutor/capabilities` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tutor/capabilities` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/sms/send (mathverse-miniapp/src/services/api.test.ts:30)
`mathverse-miniapp/src/services/api.test.ts:30` calls `GET /auth/sms/send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/sms/send` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /x (mathverse-miniapp/src/services/api.test.ts:21)
`mathverse-miniapp/src/services/api.test.ts:21` calls `GET /x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/x` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /x (mathverse-miniapp/src/services/api.test.ts:36)
`mathverse-miniapp/src/services/api.test.ts:36` calls `GET /x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/x` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /x (mathverse-miniapp/src/services/api.test.ts:41)
`mathverse-miniapp/src/services/api.test.ts:41` calls `GET /x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/x` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/mistakes/${id} (mathverse-miniapp/src/pages/mistakes/index.tsx:71)
`mathverse-miniapp/src/pages/mistakes/index.tsx:71` calls `PATCH /api/me/mistakes/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/mistakes/<p>` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/profile (mathverse-miniapp/src/stores/user.ts:86)
`mathverse-miniapp/src/stores/user.ts:86` calls `PATCH /api/me/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/profile` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/sms/send (mathverse-miniapp/src/stores/user.ts:54)
`mathverse-miniapp/src/stores/user.ts:54` calls `POST /api/auth/sms/send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/sms/send` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/sms/verify (mathverse-miniapp/src/stores/user.ts:62)
`mathverse-miniapp/src/stores/user.ts:62` calls `POST /api/auth/sms/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/sms/verify` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/wechat/mp-login (mathverse-miniapp/src/stores/user.ts:36)
`mathverse-miniapp/src/stores/user.ts:36` calls `POST /api/auth/wechat/mp-login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/wechat/mp-login` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/book/${encodeURIComponent(id)}/generate (mathverse-miniapp/src/stores/book.ts:70)
`mathverse-miniapp/src/stores/book.ts:70` calls `POST /api/book/${encodeURIComponent(id)}/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/book/<p>/generate` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/book/create (mathverse-miniapp/src/stores/book.ts:56)
`mathverse-miniapp/src/stores/book.ts:56` calls `POST /api/book/create` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/book/create` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/kb/curriculum/${stage}/seed (mathverse-miniapp/src/stores/kb.ts:100)
`mathverse-miniapp/src/stores/kb.ts:100` calls `POST /api/kb/curriculum/${stage}/seed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/kb/curriculum/<p>/seed` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/learn/exercise/generate (mathverse-miniapp/src/stores/learn.ts:101)
`mathverse-miniapp/src/stores/learn.ts:101` calls `POST /api/learn/exercise/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/learn/exercise/generate` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/learn/exercise/grade (mathverse-miniapp/src/stores/learn.ts:117)
`mathverse-miniapp/src/stores/learn.ts:117` calls `POST /api/learn/exercise/grade` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/learn/exercise/grade` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/learn/lecture (mathverse-miniapp/src/stores/learn.ts:88)
`mathverse-miniapp/src/stores/learn.ts:88` calls `POST /api/learn/lecture` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/learn/lecture` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/mistakes (mathverse-miniapp/src/stores/learn.ts:143)
`mathverse-miniapp/src/stores/learn.ts:143` calls `POST /api/me/mistakes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/mistakes` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/mistakes (mathverse-miniapp/src/stores/solve.ts:204)
`mathverse-miniapp/src/stores/solve.ts:204` calls `POST /api/me/mistakes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/mistakes` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/notebook/${encodeURIComponent(id)}/record (mathverse-miniapp/src/stores/notebook.ts:59)
`mathverse-miniapp/src/stores/notebook.ts:59` calls `POST /api/notebook/${encodeURIComponent(id)}/record` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notebook/<p>/record` If this points at an external AP…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/notebook/create (mathverse-miniapp/src/stores/notebook.ts:40)
`mathverse-miniapp/src/stores/notebook.ts:40` calls `POST /api/notebook/create` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notebook/create` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/pay/wechat/prepay (mathverse-miniapp/src/pages/membership/index.tsx:33)
`mathverse-miniapp/src/pages/membership/index.tsx:33` calls `POST /api/pay/wechat/prepay` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/pay/wechat/prepay` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/solve/deep (mathverse-miniapp/src/stores/solve.ts:133)
`mathverse-miniapp/src/stores/solve.ts:133` calls `POST /api/solve/deep` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/solve/deep` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/solve/step-explain (mathverse-miniapp/src/stores/solve.ts:187)
`mathverse-miniapp/src/stores/solve.ts:187` calls `POST /api/solve/step-explain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/solve/step-explain` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/solve/vision (mathverse-miniapp/src/stores/solve.ts:160)
`mathverse-miniapp/src/stores/solve.ts:160` calls `POST /api/solve/vision` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/solve/vision` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/solve/visualize (mathverse-miniapp/src/stores/visualize.ts:37)
`mathverse-miniapp/src/stores/visualize.ts:37` calls `POST /api/solve/visualize` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/solve/visualize` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `sms_send` without auth dependency — mathverse-api/app/routes/auth.py:206
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mathverse-api/app/routes/auth.py:206 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sms_verify` without auth dependency — mathverse-api/app/routes/auth.py:224
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mathverse-api/app/routes/auth.py:224 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `wechat_callback` without auth dependency — mathverse-api/app/routes/pay.py:101
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mathverse-api/app/routes/pay.py:101 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `wechat_mp_login` without auth dependency — mathverse-api/app/routes/auth.py:144
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mathverse-api/app/routes/auth.py:144 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 4 occurrences Foundry mined assumption checks: ZhangShiCheng3D/MathVerse
Comment chain pattern product: assumption_checks Repo: ZhangShiCheng3D/MathVerse Thread: ZhangShiCheng3D/MathVerse#8 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_artifact…
4 occurrences
repo-level (4 hits)
medium Security checks quality maintenance conf 0.70 10 occurrences Foundry mined blueprint gap alignment: ZhangShiCheng3D/MathVerse
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: …
10 occurrences
repo-level (10 hits)
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, ci. 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 Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: ghcr.io/hkuds/deeptutor:latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
deeptutor-patch/Dockerfile:23 containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: deeptutor-patch/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: mathverse-api/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/mathverse-design-review-20260601.html:101
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/mathverse-design-review-20260601.html:101 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in mathverse-api/app/main.py:25
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mathverse-api/app/main.py:25 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in mathverse-api/app/routes/pay.py:95
Found a known-risky pattern (weak_hash). Review and replace if possible.
mathverse-api/app/routes/pay.py:95 Weak hash
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DATABASE_URL`, `DEEPTUTOR_PG_BRIDGE_TIMEOUT`, `DEEPTUTOR_PG_DSN`, `DEEPTUTOR_REDIS_URL`, `DEEPTUTOR_ROLE`, `TARO_APP_API_URL`, `TARO_ENV`, `VISION_API_KEY` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
mathverse-api/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: deeptutor-patch/overlay/deeptutor/services/session/postgres_store.py:get_turn, deeptutor-patch/overlay/deeptutor/services/session/postgres_store.py:get_active_turn This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see htt…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: kb_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mathverse-api/app/services/deeptutor/rest.py:23
low System graph software Dead code conf 1.00 Possibly dead Python function: kb_supported_file_types
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mathverse-api/app/services/deeptutor/rest.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: me
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mathverse-miniapp/scripts/gen_tab_icons.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: rest_put
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
mathverse-api/app/services/deeptutor/transport.py:51
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 api Wiring conf 1.00 Unused endpoint: DELETE /{book_id}
`mathverse-api/app/routes/book.py` declares `DELETE /{book_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 /{name}
`mathverse-api/app/routes/kb.py` declares `DELETE /{name}` 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 /{notebook_id}
`mathverse-api/app/routes/notebook.py` declares `DELETE /{notebook_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/health
`mathverse-api/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/metrics
`mathverse-api/app/main.py` declares `GET /api/metrics` 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 /capabilities
`mathverse-api/app/routes/tutor.py` declares `GET /capabilities` 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 /doc/{layer}/{key}
`mathverse-api/app/routes/memory.py` declares `GET /doc/{layer}/{key}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /kg/{stage}
`mathverse-api/app/routes/learn.py` declares `GET /kg/{stage}` 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 /list
`mathverse-api/app/routes/book.py` declares `GET /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 /me
`mathverse-api/app/routes/auth.py` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /mistakes
`mathverse-api/app/routes/me.py` declares `GET /mistakes` 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 /mistakes/review-today
`mathverse-api/app/routes/me.py` declares `GET /mistakes/review-today` 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 /overview
`mathverse-api/app/routes/memory.py` declares `GET /overview` 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 /plan/today
`mathverse-api/app/routes/me.py` declares `GET /plan/today` 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 /plans
`mathverse-api/app/routes/pay.py` declares `GET /plans` 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 /progress
`mathverse-api/app/routes/me.py` declares `GET /progress` 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 /progress/radar
`mathverse-api/app/routes/me.py` declares `GET /progress/radar` 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 /recent
`mathverse-api/app/routes/dashboard.py` declares `GET /recent` 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 /score/estimate
`mathverse-api/app/routes/me.py` declares `GET /score/estimate` 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 /streak
`mathverse-api/app/routes/me.py` declares `GET /streak` 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 /subscription
`mathverse-api/app/routes/pay.py` declares `GET /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 /wechat/callback
`mathverse-api/app/routes/auth.py` declares `GET /wechat/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 /wechat/login
`mathverse-api/app/routes/auth.py` declares `GET /wechat/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 /{book_id}
`mathverse-api/app/routes/book.py` declares `GET /{book_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 /{entry_id}
`mathverse-api/app/routes/dashboard.py` declares `GET /{entry_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 /{name}/status
`mathverse-api/app/routes/kb.py` declares `GET /{name}/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 /{notebook_id}
`mathverse-api/app/routes/notebook.py` declares `GET /{notebook_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 /{question_id}
`mathverse-api/app/routes/questions.py` declares `GET /{question_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: PATCH /mistakes/{mistake_id}
`mathverse-api/app/routes/me.py` declares `PATCH /mistakes/{mistake_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: PATCH /profile
`mathverse-api/app/routes/me.py` declares `PATCH /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 api Wiring conf 1.00 Unused endpoint: POST /
`mathverse-api/app/routes/questions.py` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /create
`mathverse-api/app/routes/book.py` declares `POST /create` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /curriculum/{stage}/seed
`mathverse-api/app/routes/kb.py` declares `POST /curriculum/{stage}/seed` 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 /deep
`mathverse-api/app/routes/solve.py` declares `POST /deep` 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 /exercise/generate
`mathverse-api/app/routes/learn.py` declares `POST /exercise/generate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /exercise/grade
`mathverse-api/app/routes/learn.py` declares `POST /exercise/grade` 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 /lecture
`mathverse-api/app/routes/learn.py` declares `POST /lecture` 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 /mistakes
`mathverse-api/app/routes/me.py` declares `POST /mistakes` 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 /refresh
`mathverse-api/app/routes/auth.py` declares `POST /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 /score/estimate
`mathverse-api/app/routes/me.py` declares `POST /score/estimate` 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 /sms/send
`mathverse-api/app/routes/auth.py` declares `POST /sms/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 /sms/verify
`mathverse-api/app/routes/auth.py` declares `POST /sms/verify` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /wechat/callback
`mathverse-api/app/routes/pay.py` declares `POST /wechat/callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /wechat/mp-login
`mathverse-api/app/routes/auth.py` declares `POST /wechat/mp-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 /wechat/prepay
`mathverse-api/app/routes/pay.py` declares `POST /wechat/prepay` 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 /{book_id}/compile-page
`mathverse-api/app/routes/book.py` declares `POST /{book_id}/compile-page` 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 /{book_id}/generate
`mathverse-api/app/routes/book.py` declares `POST /{book_id}/generate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{name}/reindex
`mathverse-api/app/routes/kb.py` declares `POST /{name}/reindex` 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 /{name}/upload
`mathverse-api/app/routes/kb.py` declares `POST /{name}/upload` 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 /{notebook_id}/record
`mathverse-api/app/routes/notebook.py` declares `POST /{notebook_id}/record` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/e07a8ffa-d6ad-4420-b002-fc11d334d22b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e07a8ffa-d6ad-4420-b002-fc11d334d22b/

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.