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

wisdomproto/tangobook

https://github.com/wisdomproto/tangobook · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

325 raw signals (0 security + 325 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 325 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
47.5
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 325 findings
Critical
1
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 1 High 38 Medium 88 Low 106 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 325 Crowd 0 Layer: Software 1 Frontend 110 Hardware 3 Security 40 Cicd 2 Quality 84 Api 85
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 47.5/100 with 100.0% coverage. It contains 5764 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 325 findings — concentrated in frontend (110), api (85), quality (84). Risk profile is high: 1 critical, 38 high, 88 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 232 of 325 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in packages/client/src/features/marketing/components/project/sections/FunnelAnalyticsSection.tsx:182
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
packages/client/src/features/marketing/components/project/sections/FunnelAnalyticsSection.tsx:182 Private key in repo
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: packages/client/src/features/marketing/CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
packages/client/src/features/marketing/CLAUDE.md:293 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/mkt/storage/delete (packages/client/src/features/marketing/components/project/sections/BgmSection.tsx:79)
`packages/client/src/features/marketing/components/project/sections/BgmSection.tsx:79` calls `DELETE /api/mkt/storage/delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/storage/delete` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/mkt/storage/delete (packages/client/src/features/marketing/components/project/sections/ReferenceFilesSection.tsx:118)
`packages/client/src/features/marketing/components/project/sections/ReferenceFilesSection.tsx:118` calls `DELETE /api/mkt/storage/delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/storage/delete` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/korean-jamo-stroke-library (packages/client/src/features/phonics-learner/hooks/useKoreanJamoStrokeLibrary.ts:14)
`packages/client/src/features/phonics-learner/hooks/useKoreanJamoStrokeLibrary.ts:14` calls `GET /api/korean-jamo-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/korean-jamo-stroke-library` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/korean-jamo-stroke-library (packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:70)
`packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:70` calls `GET /api/korean-jamo-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/korean-jamo-stroke-library` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/letter-stroke-library (packages/client/src/features/phonics-learner/hooks/useLetterStrokeLibrary.ts:12)
`packages/client/src/features/phonics-learner/hooks/useLetterStrokeLibrary.ts:12` calls `GET /api/letter-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/letter-stroke-library` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/letter-stroke-library (packages/client/src/pages/LetterStrokeBulkEditorPage.tsx:63)
`packages/client/src/pages/LetterStrokeBulkEditorPage.tsx:63` calls `GET /api/letter-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/letter-stroke-library` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/mkt/storage/proxy?url=${encodeURIComponent(url)} (packages/client/src/features/marketing/hooks/use-channel-translation.ts:28)
`packages/client/src/features/marketing/hooks/use-channel-translation.ts:28` calls `GET /api/mkt/storage/proxy?url=${encodeURIComponent(url)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/storage/proxy` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/mkt/strategy/templates (packages/client/src/features/marketing/api/use-strategy-templates.ts:14)
`packages/client/src/features/marketing/api/use-strategy-templates.ts:14` calls `GET /api/mkt/strategy/templates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/strategy/templates` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.dictionaryapi.dev/api/v2/entries/en/${encodeURIComponent(key)} (packages/server/scripts/classify-key-objects-en.mjs:50)
`packages/server/scripts/classify-key-objects-en.mjs:50` calls `GET https://api.dictionaryapi.dev/api/v2/entries/en/${encodeURIComponent(key)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.dictionaryapi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.x.ai/v1/videos/${requestId} (packages/server/src/providers/grok.provider.ts:35)
`packages/server/src/providers/grok.provider.ts:35` calls `GET https://api.x.ai/v1/videos/${requestId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.x.ai/v1/videos/<p>` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://en.wiktionary.org/api/rest_v1/page/definition/${encodeURIComponent(key)} (packages/server/scripts/classify-by-page-text.mjs:80)
`packages/server/scripts/classify-by-page-text.mjs:80` calls `GET https://en.wiktionary.org/api/rest_v1/page/definition/${encodeURIComponent(key)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/en.wiktionary…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://en.wiktionary.org/api/rest_v1/page/definition/${encodeURIComponent(key)} (packages/server/scripts/classify-key-objects-wiktionary.mjs:60)
`packages/server/scripts/classify-key-objects-wiktionary.mjs:60` calls `GET https://en.wiktionary.org/api/rest_v1/page/definition/${encodeURIComponent(key)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/en.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://graph.facebook.com/v21.0/${encodeURIComponent( hashtagId )}/recent_media?user_id=${encodeURIComponent( igUserId )}&fields=id,caption,media_type,media_url,permalink,timestamp,like_count,comments_count&access_token=${accessToken} (packages/server/src/services/mkt/monitoring.service.ts:353)
`packages/server/src/services/mkt/monitoring.service.ts:353` calls `GET https://graph.facebook.com/v21.0/${encodeURIComponent( hashtagId )}/recent_media?user_id=${encodeURIComponent( igUserId )}&fields=id,caption,media_type,media_url,permalink,timestamp,like_count,comments_count…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://graph.facebook.com/v21.0/ig_hashtag_search?q=${encodeURIComponent( keyword )}&user_id=${encodeURIComponent(igUserId)}&access_token=${accessToken} (packages/server/src/services/mkt/monitoring.service.ts:343)
`packages/server/src/services/mkt/monitoring.service.ts:343` calls `GET https://graph.facebook.com/v21.0/ig_hashtag_search?q=${encodeURIComponent( keyword )}&user_id=${encodeURIComponent(igUserId)}&access_token=${accessToken}` but no backend route matches that path. This is a runtime 404 …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/ai/analyze-references (packages/client/src/features/marketing/components/project/sections/ReferenceFilesSection.tsx:141)
`packages/client/src/features/marketing/components/project/sections/ReferenceFilesSection.tsx:141` calls `POST /api/mkt/ai/analyze-references` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/ai/analyze-references…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/ai/extract-text (packages/client/src/features/marketing/components/project/sections/ReferenceFilesSection.tsx:71)
`packages/client/src/features/marketing/components/project/sections/ReferenceFilesSection.tsx:71` calls `POST /api/mkt/ai/extract-text` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/ai/extract-text` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/ai/generate (packages/client/src/features/marketing/components/content/BaseArticlePanel.tsx:133)
`packages/client/src/features/marketing/components/content/BaseArticlePanel.tsx:133` calls `POST /api/mkt/ai/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/ai/generate` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/ai/generate (packages/client/src/features/marketing/hooks/use-ai-generation.ts:23)
`packages/client/src/features/marketing/hooks/use-ai-generation.ts:23` calls `POST /api/mkt/ai/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/ai/generate` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/ai/generate-image (packages/client/src/features/marketing/hooks/use-image-generation.ts:14)
`packages/client/src/features/marketing/hooks/use-image-generation.ts:14` calls `POST /api/mkt/ai/generate-image` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/ai/generate-image` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/ai/generate-image (packages/client/src/features/marketing/store/batch-image-store.ts:102)
`packages/client/src/features/marketing/store/batch-image-store.ts:102` calls `POST /api/mkt/ai/generate-image` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/ai/generate-image` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/analytics/meta-insights (packages/client/src/features/marketing/api/use-analytics.ts:163)
`packages/client/src/features/marketing/api/use-analytics.ts:163` calls `POST /api/mkt/analytics/meta-insights` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/analytics/meta-insights` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/analytics/youtube-channel (packages/client/src/features/marketing/api/use-analytics.ts:224)
`packages/client/src/features/marketing/api/use-analytics.ts:224` calls `POST /api/mkt/analytics/youtube-channel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/analytics/youtube-channel` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/keywords/recommend (packages/client/src/features/marketing/api/use-golden-keywords.ts:25)
`packages/client/src/features/marketing/api/use-golden-keywords.ts:25` calls `POST /api/mkt/keywords/recommend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/keywords/recommend` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mkt/storage/presign (packages/client/src/features/marketing/api/use-r2-upload.ts:36)
`packages/client/src/features/marketing/api/use-r2-upload.ts:36` calls `POST /api/mkt/storage/presign` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mkt/storage/presign` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/speaking/transcribe (packages/client/src/features/games/hooks/useSpeechRecognizer.ts:202)
`packages/client/src/features/games/hooks/useSpeechRecognizer.ts:202` calls `POST /api/speaking/transcribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/speaking/transcribe` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://analyticsdata.googleapis.com/v1beta/properties/${cfg.propertyId}:runReport (packages/server/src/services/mkt/external/ga4.ts:131)
`packages/server/src/services/mkt/external/ga4.ts:131` calls `POST https://analyticsdata.googleapis.com/v1beta/properties/${cfg.propertyId}:runReport` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/analyticsd…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.dataforseo.com/v3/keywords_data/google/search_volume/live (packages/server/scripts/research-keyword-plans.mjs:63)
`packages/server/scripts/research-keyword-plans.mjs:63` calls `POST https://api.dataforseo.com/v3/keywords_data/google/search_volume/live` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.dataforseo.com/v3/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.dataforseo.com/v3/keywords_data/google/search_volume/live (packages/server/src/services/mkt/external/dataforseo.ts:95)
`packages/server/src/services/mkt/external/dataforseo.ts:95` calls `POST https://api.dataforseo.com/v3/keywords_data/google/search_volume/live` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.dataforseo.co…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.dataforseo.com/v3/serp/google/organic/live/advanced (packages/server/src/services/mkt/external/dataforseo.ts:130)
`packages/server/src/services/mkt/external/dataforseo.ts:130` calls `POST https://api.dataforseo.com/v3/serp/google/organic/live/advanced` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.dataforseo.com/v3/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.x.ai/v1/videos/generations (packages/server/src/providers/grok.provider.ts:126)
`packages/server/src/providers/grok.provider.ts:126` calls `POST https://api.x.ai/v1/videos/generations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.x.ai/v1/videos/generations` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (packages/server/src/services/mkt/external/ga4.ts:107)
`packages/server/src/services/mkt/external/ga4.ts:107` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/korean-jamo-stroke-library (packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:146)
`packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:146` calls `PUT /api/korean-jamo-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/korean-jamo-stroke-library` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/korean-jamo-stroke-library (packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:272)
`packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:272` calls `PUT /api/korean-jamo-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/korean-jamo-stroke-library` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/letter-stroke-library (packages/client/src/pages/LetterStrokeBulkEditorPage.tsx:190)
`packages/client/src/pages/LetterStrokeBulkEditorPage.tsx:190` calls `PUT /api/letter-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/letter-stroke-library` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/letter-stroke-library (packages/client/src/pages/LetterStrokeBulkEditorPage.tsx:311)
`packages/client/src/pages/LetterStrokeBulkEditorPage.tsx:311` calls `PUT /api/letter-stroke-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/letter-stroke-library` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/client/src/components/RichTextEditor.tsx:134
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/client/src/components/RichTextEditor.tsx:134 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/server/src/services/book-v2-curriculum-seed.service.ts:71
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/server/src/services/book-v2-curriculum-seed.service.ts:71 New function used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/client/src/features/blog/components/BlogPreviewModal.tsx:99
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/client/src/features/marketing/components/analytics/seo/SeoDashboard.tsx:437
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/client/src/features/marketing/components/content/BlogPreviewDialog.tsx:155
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/client/src/features/marketing/components/content/ChannelTranslationView.tsx:43
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — packages/client/src/features/marketing/components/ideas/GoldenTierCards.tsx:117
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/marketing/scripts/dataforseo-keyword-research.mjs:186
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/marketing/scripts/naver-content-keyword-research.mjs:58
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/marketing/scripts/naver-keyword-research.mjs:49
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 — packages/client/src/features/auth/api/auth.api.ts:59
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 — packages/client/src/features/games/hooks/usePhonicsMap.ts:77
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 — packages/client/src/features/games/hooks/useSpeechRecognizer.ts:202
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 — packages/client/src/features/marketing/api/use-r2-upload.ts:10
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 — packages/client/src/features/marketing/api/use-strategy-templates.ts:14
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 — packages/client/src/features/marketing/components/analytics/seo/SeoDashboard.tsx:60
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 — packages/client/src/features/marketing/components/strategy/StrategyImportDialog.tsx:63
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 — packages/client/src/features/marketing/hooks/use-channel-translation.ts:28
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 — packages/client/src/features/phonics-learner/hooks/useKoreanJamoStrokeLibrary.ts:14
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 — packages/client/src/features/phonics-learner/hooks/useLetterStrokeLibrary.ts:12
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/client/src/features/viewer/components/GameListViewer.tsx:52
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 — packages/client/src/hooks/useAssetPreloadProgress.ts:18
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/client/src/pages/KoreanJamoStrokeBulkEditorPage.tsx:272
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 — packages/server/scripts/backfill-phonics-book1-flashcard-phonemes.mjs:30
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/server/scripts/classify-by-page-text.mjs:188
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 — packages/server/scripts/classify-key-objects-strict-ko.mjs:146
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 — packages/server/scripts/convert-phonics-book1-illustrations-to-webp.mjs:94
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 — packages/server/scripts/dump-non-noun-key-objects.mjs:66
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 — packages/server/scripts/research-keyword-plans.mjs:63
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 — packages/server/scripts/scan-untranslated-keyobjects.mjs:16
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 — packages/server/scripts/seed-letter-tracing-points-book1.mjs:546
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 — packages/server/scripts/seed-letter-tracing-strokes-book1.mjs:354
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 — packages/server/scripts/sync-phonics-book1-targetwords.mjs:35
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/server/scripts/verify-key-object-in-page-text.mjs:35
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/server/src/providers/grok.provider.ts:75
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 — packages/server/src/providers/naver.provider.ts:38
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 — packages/server/src/services/book-v2.service.ts:323
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 — packages/server/src/services/mkt/external/ga4.ts:107
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 — packages/server/src/services/mkt/external/youtube-data.ts:120
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 — packages/server/src/services/mkt/publish.service.ts:79
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/generate-pixar-3d-jack.mjs:15
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/seed-hori-stub.mjs:40
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: packages/client/src/features/arcade-games/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
packages/client/src/features/arcade-games/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: packages/client/src/features/longform-video/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
packages/client/src/features/longform-video/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: packages/client/src/features/marketing/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
packages/client/src/features/marketing/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: packages/client/src/features/rewards/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
packages/client/src/features/rewards/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, operator-readme, lockfile. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, operator-readme, lockfile. 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `/marketing/*` has no Link/navigate to it — packages/client/src/features/marketing/pages/MarketingLayout.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/reset-pin/index.ts:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/reset-pin/index.ts:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/client/src/features/blog/components/BlogPreviewModal.tsx:99
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/client/src/features/blog/components/BlogPreviewModal.tsx:99 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/client/src/features/marketing/components/analytics/seo/SeoDashboard.tsx:437
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/client/src/features/marketing/components/analytics/seo/SeoDashboard.tsx:437 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/client/src/features/marketing/components/content/BlogPreviewDialog.tsx:155
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/client/src/features/marketing/components/content/BlogPreviewDialog.tsx:155 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/client/src/features/marketing/components/content/ChannelTranslationView.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/client/src/features/marketing/components/content/ChannelTranslationView.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in packages/client/src/features/marketing/components/ideas/GoldenTierCards.tsx:117
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
packages/client/src/features/marketing/components/ideas/GoldenTierCards.tsx:117 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/books/curriculum-master.html:457
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/books/curriculum-master.html:457 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/books/vocabulary-master-ko.html:388
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/books/vocabulary-master-ko.html:388 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/books/vocabulary-master.html:403
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/books/vocabulary-master.html:403 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/public/curriculum-master.html:457
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/public/curriculum-master.html:457 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/public/design-system.html:566
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/public/design-system.html:566 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/public/key-object-editor.html:232
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/public/key-object-editor.html:232 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/public/vocabulary-master-ko.html:388
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/public/vocabulary-master-ko.html:388 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/public/vocabulary-master.html:426
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/public/vocabulary-master.html:426 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/public/vocabulary-table-ko.html:397
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/public/vocabulary-table-ko.html:397 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/components/RichTextEditor.tsx:106
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/components/RichTextEditor.tsx:106 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/features/blog/components/BlogPreviewModal.tsx:58
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/features/blog/components/BlogPreviewModal.tsx:58 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/features/games/components/players/EnglishBlockPlayer.tsx:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/features/games/components/players/EnglishBlockPlayer.tsx:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/features/marketing/components/content/BlogCardItem.tsx:23
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/features/marketing/components/content/BlogCardItem.tsx:23 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in packages/client/src/features/marketing/lib/strategy-html-parser.ts:93
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
packages/client/src/features/marketing/lib/strategy-html-parser.ts:93 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in docs/books/curriculum-master.html:500
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
docs/books/curriculum-master.html:500 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in packages/client/public/curriculum-master.html:500
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
packages/client/public/curriculum-master.html:500 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/scripts/convert-phonics-book1-illustrations-to-webp.mjs:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/scripts/convert-phonics-book1-illustrations-to-webp.mjs:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/scripts/convert-png-to-webp.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/scripts/convert-png-to-webp.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/scripts/merge-and-apply-batch.mjs:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/scripts/merge-and-apply-batch.mjs:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/scripts/normalize-bgm-volume.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/scripts/normalize-bgm-volume.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/scripts/strip-checkerboard-bg.mjs:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/scripts/strip-checkerboard-bg.mjs:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/providers/longform.provider.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/providers/longform.provider.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/services/book-v2.service.ts:67
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/services/book-v2.service.ts:67 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/services/longform.service.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/services/longform.service.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/services/phonics-library.service.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/services/phonics-library.service.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/utils/audio-duration.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/utils/audio-duration.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/utils/transcode.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/utils/transcode.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/synthesize-game-sfx.mjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/synthesize-game-sfx.mjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/synthesize-runner-sfx.mjs:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/synthesize-runner-sfx.mjs:7 Node child process
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 284 placeholder/mock markers across 105 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality 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
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — packages/client/src/features/phonics-learner/components/EnglishPhonicsStudyPage.tsx:198
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — packages/client/src/features/phonics-learner/components/KoreanPhonicsStudyPage.tsx:244
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 11 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `API_BASE`, `CHROMIUM_PATH`, `OPENAI_API_KEY`, `SERVER_URL`, `TEMP`, `VITE_SUPABASE_ANON_KEY`, `VITE_SUPABASE_URL`, `XAI_API_KEY` + 3 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 1133 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — packages/client/src/features/blog/components/BlogPreviewModal.tsx:88
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 — packages/client/src/features/book-v2/components/AudiobookRenderModal.tsx:101
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 — packages/client/src/features/book-v2/components/BookListSidebar.tsx:253
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 — packages/client/src/features/book-v2/components/CaptionsModal.tsx:142
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 — packages/client/src/features/book-v2/components/CreateLongformModal.tsx:52
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 — packages/client/src/features/book-v2/components/SceneEditor.tsx:65
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 — packages/client/src/features/book-v2/components/YouTubeUploadModal.tsx:179
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 — packages/client/src/features/card-news/components/CardNewsPreviewModal.tsx:158
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 — packages/client/src/features/card-news/components/CardNewsSlideEditor.tsx:75
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 — packages/client/src/features/games/components/DotEditorModal.tsx:48
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 — packages/client/src/features/games/components/GameCreatorModal.tsx:65
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 — packages/client/src/features/games/components/GamePreviewModal.tsx:43
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 — packages/client/src/features/key-object/components/KeyObjectDotEditorModal.tsx:39
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 — packages/client/src/features/phonics/components/HotspotEditorModal.tsx:317
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
115 tests / 988 src (ratio 0.12).
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/client/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/remotion/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/remotion/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/server/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/shared/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `__legacy` in packages/client/src/features/longform-video/lib/group-by-style.ts:3
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rest_v1` in packages/server/scripts/classify-by-page-text.mjs:81
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rest_v1` in packages/server/scripts/classify-key-objects-wiktionary.mjs:61
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 `totalOld` in packages/server/src/scripts/migrate-assets.ts:35
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: download_file
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
packages/server/scripts/generate_longform.py:55
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 — packages/server/src/providers/grok.provider.ts:58
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 — packages/server/src/providers/longform.provider.ts:121
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 — packages/server/src/providers/youtube.provider.ts:120
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 — packages/server/src/scripts/check-storybook-urls.ts:28
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 — packages/server/src/scripts/count-manifests.ts:6
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 — packages/server/src/scripts/find-storybook.ts:11
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 — packages/server/src/scripts/migrate-assets.ts:33
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 — packages/server/src/scripts/restore-from-manifest.ts:12
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 — packages/server/src/scripts/verify-transcode.ts:15
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 — packages/server/src/scripts/verify-url-walker.ts:7
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 — packages/server/src/services/audiobook.service.ts:70
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 — packages/server/src/services/longform.service.ts:717
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 — packages/server/src/services/mkt/external/__tests__/naver-searchad.test.ts:13
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 — packages/server/src/services/storybook.service.ts:206
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 — packages/server/src/utils/remotion-bundle.ts:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /reset
`packages/server/src/routes/vocabulary-db.routes.ts` declares `DELETE /reset` 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 /
`packages/server/src/routes/vocabulary-db.routes.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/debug/logs
`packages/server/src/app.ts` declares `GET /api/debug/logs` 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/r2-proxy
`packages/server/src/app.ts` declares `GET /api/r2-proxy` 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 /catalog
`packages/server/src/routes/hori.routes.ts` declares `GET /catalog` 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 /storybook/:storybookId
`packages/server/src/routes/vocabulary-db.routes.ts` declares `GET /storybook/:storybookId` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /word-pool/by-categories
`packages/server/src/routes/playground.routes.ts` declares `GET /word-pool/by-categories` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /word-pool/sample
`packages/server/src/routes/playground.routes.ts` declares `GET /word-pool/sample` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /word/:word
`packages/server/src/routes/vocabulary-db.routes.ts` declares `GET /word/:word` 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 /{*path}
`packages/server/src/app.ts` declares `GET /{*path}` 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 /blog/generate
`packages/server/src/routes/marketing.routes.ts` declares `POST /blog/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 /blog/generate-config
`packages/server/src/routes/marketing.routes.ts` declares `POST /blog/generate-config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /bulk-sync
`packages/server/src/routes/vocabulary-db.routes.ts` declares `POST /bulk-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 /images/analyze-style
`packages/client/src/features/settings/api/settings.api.ts` declares `POST /images/analyze-style` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /images/download-zip
`packages/client/src/features/illustration/components/PagesTab.tsx` declares `POST /images/download-zip` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /images/upload-audio
`packages/client/src/features/settings/api/settings.api.ts` declares `POST /images/upload-audio` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /items
`packages/server/src/routes/hori.routes.ts` declares `POST /items` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /phonics-library/upload
`packages/client/src/features/settings/api/settings.api.ts` declares `POST /phonics-library/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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sync
`packages/server/src/routes/vocabulary-db.routes.ts` declares `POST /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 /system-sounds/upload
`packages/client/src/features/settings/api/settings.api.ts` declares `POST /system-sounds/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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /word-pool/enrich
`packages/server/src/routes/playground.routes.ts` declares `POST /word-pool/enrich` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/admin/book-v2
`packages/server/src/app.ts` declares `USE /api/admin/book-v2` 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: USE /api/art-style-library
`packages/server/src/app.ts` declares `USE /api/art-style-library` 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: USE /api/audiobooks
`packages/server/src/app.ts` declares `USE /api/audiobooks` 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: USE /api/character-library
`packages/server/src/app.ts` declares `USE /api/character-library` 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: USE /api/games
`packages/server/src/app.ts` declares `USE /api/games` 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: USE /api/hori
`packages/server/src/app.ts` declares `USE /api/hori` 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: USE /api/images
`packages/server/src/app.ts` declares `USE /api/images` 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: USE /api/korean-jamo-stroke-library
`packages/server/src/app.ts` declares `USE /api/korean-jamo-stroke-library` 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: USE /api/letter-stroke-library
`packages/server/src/app.ts` declares `USE /api/letter-stroke-library` 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: USE /api/library-config
`packages/server/src/app.ts` declares `USE /api/library-config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/longform
`packages/server/src/app.ts` declares `USE /api/longform` 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: USE /api/marketing
`packages/server/src/app.ts` declares `USE /api/marketing` 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: USE /api/mkt
`packages/server/src/app.ts` declares `USE /api/mkt` 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: USE /api/phonics
`packages/server/src/app.ts` declares `USE /api/phonics` 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: USE /api/phonics-library
`packages/server/src/app.ts` declares `USE /api/phonics-library` 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: USE /api/playground
`packages/server/src/app.ts` declares `USE /api/playground` 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: USE /api/prompt-presets
`packages/server/src/app.ts` declares `USE /api/prompt-presets` 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: USE /api/quiz
`packages/server/src/app.ts` declares `USE /api/quiz` 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: USE /api/settings
`packages/server/src/app.ts` declares `USE /api/settings` 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: USE /api/speaking
`packages/server/src/app.ts` declares `USE /api/speaking` 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: USE /api/storybooks
`packages/server/src/app.ts` declares `USE /api/storybooks` 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: USE /api/system-sounds
`packages/server/src/app.ts` declares `USE /api/system-sounds` 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: USE /api/translation
`packages/server/src/app.ts` declares `USE /api/translation` 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: USE /api/tts
`packages/server/src/app.ts` declares `USE /api/tts` 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: USE /api/v2/books
`packages/server/src/app.ts` declares `USE /api/v2/books` 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: USE /api/vocab-overrides
`packages/server/src/app.ts` declares `USE /api/vocab-overrides` 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: USE /api/vocabulary-db
`packages/server/src/app.ts` declares `USE /api/vocabulary-db` 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: USE /api/vocabulary-units
`packages/server/src/app.ts` declares `USE /api/vocabulary-units` 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: USE /api/youtube-presets
`packages/server/src/app.ts` declares `USE /api/youtube-presets` 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: packages/client/src/features/arcade-games/hori-run/scenes/GameScene.ts (1717 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/client/src/features/audiobook/components/AudiobookProjectCard.tsx (1896 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/client/src/features/longform-video/components/RenderStep.tsx (1574 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/client/src/features/marketing/components/content/CardNewsPanel.tsx (1285 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/server/src/services/book-v2.service.ts (2065 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/server/src/services/longform.service.ts (1717 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/shared/src/constants/index.ts (1737 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/19e6f46a-b4a8-4fdf-a7c5-a0c6896c80a5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/19e6f46a-b4a8-4fdf-a7c5-a0c6896c80a5/

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.