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

shock11090304-a11y/ai-juku-system

https://github.com/shock11090304-a11y/ai-juku-system · scanned 2026-06-16 00:11 UTC (2 months, 2 weeks ago)

255 raw signals (0 security + 255 graph)

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

Complete repo analysis

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

JSON
Combined
78.8
/100
Security checks
79
0 findings
System graph
79
100.0% cov · 217 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 23 Medium 75 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 217 Crowd 0 Layer: Software 7 Frontend 9 Network 2 Hardware 1 Security 59 Cicd 1 Quality 65 Api 73
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 78.8/100 with 100.0% coverage. It contains 2453 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 255 findings — concentrated in quality (80), api (73), security (59). Risk profile is high: 0 critical, 23 high, 75 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/course-applications?status=pending&limit=100 (ceo.js:2164)
`ceo.js:2164` calls `GET /api/admin/course-applications?status=pending&limit=100` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/course-applications` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/db/r2-backups?limit=30 (ceo.js:2281)
`ceo.js:2281` calls `GET /api/admin/db/r2-backups?limit=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/db/r2-backups` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/messages/${encodeURIComponent(id)}/attachment (ceo.js:1936)
`ceo.js:1936` calls `GET /api/admin/messages/${encodeURIComponent(id)}/attachment` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/messages/<p>/attachment` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /payment/api/admin-charge-history?month=${encodeURIComponent(month)}&type=${encodeURIComponent(type)} (payment/app.js:2699)
`payment/app.js:2699` calls `GET /payment/api/admin-charge-history?month=${encodeURIComponent(month)}&type=${encodeURIComponent(type)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-history…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /payment/api/admin-charge-month-end-preview (payment/app.js:2281)
`payment/app.js:2281` calls `GET /payment/api/admin-charge-month-end-preview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-month-end-preview` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /payment/api/registered-customers (payment/app.js:1388)
`payment/app.js:1388` calls `GET /payment/api/registered-customers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/registered-customers` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8080/default_data.json (app.js:9148)
`app.js:9148` calls `GET http://localhost:8080/default_data.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8080/default_data.json` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8080/default_data.json (personalized-outreach.js:43)
`personalized-outreach.js:43` calls `GET http://localhost:8080/default_data.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8080/default_data.json` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/ai-draft (ceo.js:2062)
`ceo.js:2062` calls `POST /api/admin/ai-draft` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/ai-draft` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/course-applications/${encodeURIComponent(id)}/approve (ceo.js:2205)
`ceo.js:2205` calls `POST /api/admin/course-applications/${encodeURIComponent(id)}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/course-applications/<p>/approve` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/course-applications/${encodeURIComponent(id)}/reject (ceo.js:2227)
`ceo.js:2227` calls `POST /api/admin/course-applications/${encodeURIComponent(id)}/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/course-applications/<p>/reject` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/db/snapshot-to-r2 (ceo.js:2339)
`ceo.js:2339` calls `POST /api/admin/db/snapshot-to-r2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/db/snapshot-to-r2` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-charge-month-end-execute (payment/app.js:2467)
`payment/app.js:2467` calls `POST /payment/api/admin-charge-month-end-execute` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-month-end-execute` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-charge-month-end-execute (payment/app.js:2490)
`payment/app.js:2490` calls `POST /payment/api/admin-charge-month-end-execute` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-month-end-execute` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-charge-reconcile (payment/app.js:2875)
`payment/app.js:2875` calls `POST /payment/api/admin-charge-reconcile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-reconcile` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-charge-reconcile (payment/app.js:2908)
`payment/app.js:2908` calls `POST /payment/api/admin-charge-reconcile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-reconcile` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-charge-reconcile (payment/app.js:2915)
`payment/app.js:2915` calls `POST /payment/api/admin-charge-reconcile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-charge-reconcile` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-registration-cancel (payment/app.js:2952)
`payment/app.js:2952` calls `POST /payment/api/admin-registration-cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-registration-cancel` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/admin-update-registration (payment/app.js:672)
`payment/app.js:672` calls `POST /payment/api/admin-update-registration` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/admin-update-registration` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/mail-send (payment/app.js:4711)
`payment/app.js:4711` calls `POST /payment/api/mail-send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/mail-send` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/mail-send (payment/app.js:4763)
`payment/app.js:4763` calls `POST /payment/api/mail-send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/mail-send` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/past-due-invoice (payment/app.js:1986)
`payment/app.js:1986` calls `POST /payment/api/past-due-invoice` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/past-due-invoice` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /payment/api/past-due-invoice (payment/app.js:2043)
`payment/app.js:2043` calls `POST /payment/api/past-due-invoice` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payment/api/past-due-invoice` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app.js:3522
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — auth-guard.js:86
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ceo.js:1080
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — english-exam.js:725
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mock-exam.js:292
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mypage.js:274
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — payment/app.js:1019
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — personalized-outreach.js:24
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — textbook-generator.js:469
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 security security conf 1.00 Insecure pattern 'cors_wildcard' in api/register-subscribe.py:493
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/register-subscribe.py:493 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin-only.js:32
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin-only.js:32 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ai-tutor-photo.html:147
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ai-tutor-photo.html:147 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in alerts.js:71
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
alerts.js:71 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in article.html:124
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
article.html:124 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in auth.html:150
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
auth.html:150 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in blog.html:136
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
blog.html:136 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ceo.html:1019
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ceo.html:1019 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ceo.js:156
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ceo.js:156 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in checkout-success.html:302
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
checkout-success.html:302 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in checkout.html:328
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
checkout.html:328 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in checkout.js:151
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
checkout.js:151 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in content-studio.js:44
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
content-studio.js:44 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in demo-features.js:325
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
demo-features.js:325 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dojo-drill.html:289
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dojo-drill.html:289 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in english-exam.js:901
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
english-exam.js:901 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in exam-prep.html:113
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
exam-prep.html:113 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in exam-prep.js:83
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
exam-prep.js:83 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:1528
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:1528 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in instagram-cta.html:201
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
instagram-cta.html:201 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in learning-brain.js:312
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
learning-brain.js:312 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in login.html:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
login.html:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in lp.html:1102
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
lp.html:1102 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in material-scan.html:106
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
material-scan.html:106 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in mock-exam.js:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
mock-exam.js:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in mypage.html:203
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
mypage.html:203 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in mypage.js:294
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
mypage.js:294 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in payment/app.js:133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
payment/app.js:133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in payment/chat.html:318
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
payment/chat.html:318 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in payment/register.html:442
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
payment/register.html:442 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in personalized-outreach.js:292
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
personalized-outreach.js:292 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pwa.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pwa.js:37 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in quick-start.js:196
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
quick-start.js:196 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in referral-program.js:128
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
referral-program.js:128 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in referral.html:252
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
referral.html:252 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in safety-school.js:166
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
safety-school.js:166 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in social-proof.js:39
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
social-proof.js:39 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in student-upgrade.html:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
student-upgrade.html:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in success-stories.js:199
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
success-stories.js:199 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in support.html:238
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
support.html:238 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in textbook-generator.js:87
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
textbook-generator.js:87 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in university-exam.html:318
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
university-exam.html:318 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in video-ads.js:59
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
video-ads.js:59 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in vocab.js:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
vocab.js:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in app.js:8069
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
app.js:8069 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in ceo.html:8403
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
ceo.html:8403 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in ceo.html:4209
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
ceo.html:4209 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in university-exam.html:916
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
university-exam.html:916 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in analytics.js:33
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
analytics.js:33 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in app.js:788
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
app.js:788 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in auth.html:241
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
auth.html:241 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in ceo.html:7481
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
ceo.html:7481 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend-error-monitor.js:26
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend-error-monitor.js:26 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in login.html:366
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
login.html:366 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — marketing-assets/generate_reels_video.py:519
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — marketing-assets/generate_reels_video_v2.py:486
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 122 placeholder/mock markers across 17 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 network Security conf 1.00 Privileged port 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
render.yaml Ports
medium System graph network Security conf 1.00 Privileged port 20 in use
Port 20 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
render.yaml Ports
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 110 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AUDIT_BASE`, `CHAT_ADMIN_PASSWORD`, `CHAT_SIGNING_SECRET`, `DATABASE_URL`, `KV_REST_API_TOKEN`, `KV_REST_API_URL`, `PUBLIC_BASE_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 323 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — ceo.js:2047
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — mypage.js:2137
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — pwa.js:46
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph security security conf 1.00 Insecure pattern 'document_write' in app.js:8953
Found a known-risky pattern (document_write). Review and replace if possible.
app.js:8953 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in mypage.html:1765
Found a known-risky pattern (document_write). Review and replace if possible.
mypage.html:1765 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in mypage.js:3895
Found a known-risky pattern (document_write). Review and replace if possible.
mypage.js:3895 Document write
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: api/admin-registration-cancel.py:do_POST, api/admin-charge-reconcile.py:do_POST 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.
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/generate_coaching_guide_v6.py:fig_subject_hensachi, scripts/generate_coaching_guide_v3.py:fig_subject_hensachi, scripts/generate_coaching_guide_v4.py:fig_subject_hensachi This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: scripts/generate_coaching_guide_v6.py:fig_hensachi_trend, scripts/generate_coaching_guide_v2.py:fig_hensachi_trend, scripts/generate_coaching_guide_v3.py:fig_hensachi_trend, scripts/generate_coaching_guide_v4.py:fig_hensachi_trend This is *the* AI-co…
6 occurrences
repo-level (6 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: api/admin-charge-month-end-preview.py:do_GET, api/admin-charge-month-end-execute.py:do_POST, api/registered-customers.py:do_GET, api/admin-charge-history.py:do_GET This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see htt…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 8 places
Functions with the same first-5-line body hash: scripts/generate_coaching_guide_v6.py:wrap, scripts/generate_coaching_guide_v6.py:wrap, scripts/generate_coaching_guide_v2.py:wrap, scripts/generate_coaching_guide_v2.py:wrap This is *the* AI-coder failure mode (4× more duplication in vibe-coded repo…
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 quality Integrity conf 1.00 Old/deprecated-named symbol `AI_Coaching_Guide_v2` in scripts/generate_coaching_guide_v2.py:10
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 `AI_Coaching_Guide_v2` in scripts/generate_coaching_guide_v3.py:10
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 `AI_Coaching_Guide_v2` in scripts/generate_coaching_guide_v4.py:10
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 `AI_Coaching_Guide_v2` in scripts/generate_coaching_guide_v6.py:10
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 `ai_juku_problem_stats_v1` in app.js:8141
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 `ai_juku_sw_purge_log_v2` in cache-purge.js:48
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 `bcc_copy` in payment/app.js:4810
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 `ee_qpref_v1` in english-exam.js:2293
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 `generate_reels_video_v2` in marketing-assets/generate_reels_video_v2.py:4
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 6 occurrences Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
6 files, 6 locations
api/admin-charge-history.py:115
api/admin-charge-month-end-preview.py:97
api/chat.py:230
api/mail-send.py:224
api/registered-customers.py:81
api/stripe-charges.py:119
low System graph software Dead code conf 1.00 Possibly dead Python function: do_OPTIONS
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/register-subscribe.py:490
low System graph software Dead code conf 1.00 8 occurrences Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
8 files, 8 locations
api/admin-charge-month-end-execute.py:166
api/admin-charge-reconcile.py:130
api/admin-registration-cancel.py:101
api/chat.py:287
api/mail-send.py:132
api/past-due-invoice.py:280
api/register-subscribe.py:331
api/stripe-webhook.py:487
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: draw
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
scripts/generate_coaching_guide_v2.py:396
scripts/generate_coaching_guide_v3.py:792
scripts/generate_coaching_guide_v6.py:801
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: first_page
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
scripts/generate_coaching_guide_v2.py:301
scripts/generate_coaching_guide_v3.py:697
scripts/generate_coaching_guide_v4.py:706
scripts/generate_coaching_guide_v6.py:706
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: later_page
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
scripts/generate_coaching_guide_v2.py:314
scripts/generate_coaching_guide_v3.py:710
scripts/generate_coaching_guide_v4.py:719
scripts/generate_coaching_guide_v6.py:719
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: wrap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
scripts/generate_coaching_guide_v2.py:395
scripts/generate_coaching_guide_v3.py:791
scripts/generate_coaching_guide_v4.py:800
scripts/generate_coaching_guide_v6.py:800
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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.js:3892
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — english-exam.js:1676
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — payment/app.js:974
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — personalized-outreach.js:50
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — textbook-generator.js:552
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 /api/admin/analytics
`server/main.py` declares `GET /api/admin/analytics` 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/lesson-prints/stats
`server/main.py` declares `GET /api/admin/lesson-prints/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/marketing/custom-gpt-announcement-templates
`server/main.py` declares `GET /api/admin/marketing/custom-gpt-announcement-templates` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/marketing/custom-gpt-funnel-specs
`server/main.py` declares `GET /api/admin/marketing/custom-gpt-funnel-specs` 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/monitor/rollback-history
`server/main.py` declares `GET /api/admin/monitor/rollback-history` 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/revenue-timeline
`server/main.py` declares `GET /api/admin/revenue-timeline` 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/stripe/check-prices
`server/main.py` declares `GET /api/admin/stripe/check-prices` 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/stripe/diagnose-orphan-subs
`server/main.py` declares `GET /api/admin/stripe/diagnose-orphan-subs` 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/stripe/diagnose-trialing-leftovers
`server/main.py` declares `GET /api/admin/stripe/diagnose-trialing-leftovers` 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/verify
`server/main.py` declares `GET /api/admin/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: GET /api/admin/weakness-heatmap
`server/main.py` declares `GET /api/admin/weakness-heatmap` 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/auth/verify
`server/main.py` declares `GET /api/auth/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: GET /api/email/diagnose-public
`server/main.py` declares `GET /api/email/diagnose-public` 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
`server/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/marketing/verify-invite
`server/main.py` declares `GET /api/marketing/verify-invite` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/stats
`server/main.py` declares `GET /api/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/student/admission-likelihood
`server/main.py` declares `GET /api/student/admission-likelihood` 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/student/lesson-prints
`server/main.py` declares `GET /api/student/lesson-prints` 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/student/lesson-prints/by-goal
`server/main.py` declares `GET /api/student/lesson-prints/by-goal` 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/student/lesson-prints/recommended
`server/main.py` declares `GET /api/student/lesson-prints/recommended` 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/student/weakness-progress
`server/main.py` declares `GET /api/student/weakness-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 /api/student/weakness-top3
`server/main.py` declares `GET /api/student/weakness-top3` 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/student/worksheet/history
`server/main.py` declares `GET /api/student/worksheet/history` 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/student/worksheet/this-week
`server/main.py` declares `GET /api/student/worksheet/this-week` 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 /api/student/profile
`server/main.py` declares `PATCH /api/student/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 /api/admin/anthropic/credit-monitor-now
`server/main.py` declares `POST /api/admin/anthropic/credit-monitor-now` 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/dalle/generate
`server/main.py` declares `POST /api/admin/dalle/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 /api/admin/git/apply-patch
`server/main.py` declares `POST /api/admin/git/apply-patch` 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/lesson-prints/sync
`server/main.py` declares `POST /api/admin/lesson-prints/sync` 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/login
`server/main.py` declares `POST /api/admin/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 /api/admin/marketing/bulk-invite
`server/main.py` declares `POST /api/admin/marketing/bulk-invite` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/marketing/generate-invite-code
`server/main.py` declares `POST /api/admin/marketing/generate-invite-code` 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/marketing/generate-student-invite
`server/main.py` declares `POST /api/admin/marketing/generate-student-invite` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/marketing/send-ig-carousel
`server/main.py` declares `POST /api/admin/marketing/send-ig-carousel` 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/marketing/send-link-email
`server/main.py` declares `POST /api/admin/marketing/send-link-email` 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/monitor/auto-rollback
`server/main.py` declares `POST /api/admin/monitor/auto-rollback` 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/stripe/backfill-payments
`server/main.py` declares `POST /api/admin/stripe/backfill-payments` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/stripe/reconcile
`server/main.py` declares `POST /api/admin/stripe/reconcile` 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/stripe/setup-all-prices
`server/main.py` declares `POST /api/admin/stripe/setup-all-prices` 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/stripe/setup-founder-special
`server/main.py` declares `POST /api/admin/stripe/setup-founder-special` 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/stripe/setup-threads6k-coupon
`server/main.py` declares `POST /api/admin/stripe/setup-threads6k-coupon` 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/stripe/webhook-events-sync
`server/main.py` declares `POST /api/admin/stripe/webhook-events-sync` 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/textbooks/generate-figure
`server/main.py` declares `POST /api/admin/textbooks/generate-figure` 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/tts/generate
`server/main.py` declares `POST /api/admin/tts/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 /api/admin/weakness/aggregate-now
`server/main.py` declares `POST /api/admin/weakness/aggregate-now` 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/worksheet/run-weekly-now
`server/main.py` declares `POST /api/admin/worksheet/run-weekly-now` 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/ai/messages
`server/main.py` declares `POST /api/ai/messages` 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/auth/magic-link
`server/main.py` declares `POST /api/auth/magic-link` 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/auth/verify-code
`server/main.py` declares `POST /api/auth/verify-code` 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/student/lesson-prints/{print_id}/download
`server/main.py` declares `POST /api/student/lesson-prints/{print_id}/download` 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.js (10426 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ceo.js (2385 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: english-exam.js (5524 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: mypage.js (5173 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: payment/app.js (5953 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/generate_coaching_guide_v2.py (1246 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/generate_coaching_guide_v3.py (2055 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/generate_coaching_guide_v4.py (2729 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/generate_coaching_guide_v6.py (2554 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: textbook-generator.js (1528 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/e5b1eac8-ce4d-453e-a4b0-03dfad127634/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e5b1eac8-ce4d-453e-a4b0-03dfad127634/

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.