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

shuitian23-bot/lexiang-workbench

https://github.com/shuitian23-bot/lexiang-workbench · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

305 raw signals (0 security + 305 graph)

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

Complete repo analysis

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

JSON
Combined
53.8
/100
Security checks
54
0 findings
System graph
54
100.0% cov · 303 findings
Critical
3
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 105 Medium 70 Low 124 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 303 Crowd 0 Layer: Software 7 Frontend 46 Security 40 Cicd 1 Quality 54 Api 155
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 53.8/100 with 100.0% coverage. It contains 2519 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 305 findings — concentrated in api (155), quality (55), frontend (46). Risk profile is high: 4 critical, 105 high, 70 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in routes/geo-dashboard.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
routes/geo-dashboard.js:6
critical System graph security Secrets conf 1.00 Possible secret in scripts/batch_biz_wiki.py
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
scripts/batch_biz_wiki.py:29
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in scripts/p1_add_warnings.py
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
lines 7
scripts/p1_add_warnings.py:7 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/marketing-tasks/${id} (public/admin/workbench-data.js:1538)
`public/admin/workbench-data.js:1538` calls `DELETE /api/admin/marketing-tasks/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/marketing-tasks/<p>` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/personas/${id} (public/admin/workbench-data.js:538)
`public/admin/workbench-data.js:538` calls `DELETE /api/admin/personas/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/personas/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/product-categories/${id} (public/admin/workbench-data.js:1423)
`public/admin/workbench-data.js:1423` calls `DELETE /api/admin/product-categories/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/product-categories/<p>` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/products/${id} (public/admin/workbench-data.js:1377)
`public/admin/workbench-data.js:1377` calls `DELETE /api/admin/products/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/products/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/regression-cases/${id} (public/admin/workbench-data.js:652)
`public/admin/workbench-data.js:652` calls `DELETE /api/admin/regression-cases/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/regression-cases/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/users/${id} (public/admin/workbench-data.js:498)
`public/admin/workbench-data.js:498` calls `DELETE /api/admin/users/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /aiadmin/proxy/new/smart/touch/material/event/list (public/admin/workbench-data.js:2081)
`public/admin/workbench-data.js:2081` calls `GET /aiadmin/proxy/new/smart/touch/material/event/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/aiadmin/proxy/new/smart/touch/material/event/list` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /aiadmin/proxy/new/smart/touch/user/tag/group/all (public/admin/workbench-data.js:2064)
`public/admin/workbench-data.js:2064` calls `GET /aiadmin/proxy/new/smart/touch/user/tag/group/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/aiadmin/proxy/new/smart/touch/user/tag/group/all` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /aiadmin/proxy/new/smart/touch/user/tag/profile/all (public/admin/workbench-data.js:2075)
`public/admin/workbench-data.js:2075` calls `GET /aiadmin/proxy/new/smart/touch/user/tag/profile/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/aiadmin/proxy/new/smart/touch/user/tag/profile/all` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /aiadmin/proxy/old/cdashboard/dashboard/area (public/admin/workbench-data.js:1922)
`public/admin/workbench-data.js:1922` calls `GET /aiadmin/proxy/old/cdashboard/dashboard/area` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/aiadmin/proxy/old/cdashboard/dashboard/area` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /aiadmin/proxy/old/cdashboard/dashboard/channel (public/admin/workbench-data.js:1921)
`public/admin/workbench-data.js:1921` calls `GET /aiadmin/proxy/old/cdashboard/dashboard/channel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/aiadmin/proxy/old/cdashboard/dashboard/channel` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/bot-config (public/admin/workbench-data.js:1175)
`public/admin/workbench-data.js:1175` calls `GET /api/admin/bot-config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-config` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/conversations/${convId} (public/admin/workbench-data.js:319)
`public/admin/workbench-data.js:319` calls `GET /api/admin/conversations/${convId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/conversations/<p>` 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/conversations?limit=50 (public/admin/workbench-data.js:297)
`public/admin/workbench-data.js:297` calls `GET /api/admin/conversations?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/conversations` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/evolution-notes (public/admin/workbench-data.js:580)
`public/admin/workbench-data.js:580` calls `GET /api/admin/evolution-notes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/evolution-notes` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/experiments (public/admin/workbench-data.js:1601)
`public/admin/workbench-data.js:1601` calls `GET /api/admin/experiments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/experiments` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/learning-status (public/admin/workbench-data.js:580)
`public/admin/workbench-data.js:580` calls `GET /api/admin/learning-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/learning-status` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/logs?limit=50 (public/admin/workbench-data.js:1222)
`public/admin/workbench-data.js:1222` calls `GET /api/admin/logs?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/logs` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/marketing-tasks (public/admin/workbench-data.js:1432)
`public/admin/workbench-data.js:1432` calls `GET /api/admin/marketing-tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/marketing-tasks` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/marketing-tasks (public/admin/workbench-data.js:1494)
`public/admin/workbench-data.js:1494` calls `GET /api/admin/marketing-tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/marketing-tasks` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/metrics (public/admin/workbench-data.js:544)
`public/admin/workbench-data.js:544` calls `GET /api/admin/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/metrics` 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/personas (public/admin/workbench-data.js:505)
`public/admin/workbench-data.js:505` calls `GET /api/admin/personas` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/personas` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/product-categories (public/admin/workbench-data.js:1250)
`public/admin/workbench-data.js:1250` calls `GET /api/admin/product-categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/product-categories` 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 /api/admin/product-categories (public/admin/workbench-data.js:1386)
`public/admin/workbench-data.js:1386` calls `GET /api/admin/product-categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/product-categories` 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 /api/admin/products/${editId} (public/admin/workbench-data.js:1317)
`public/admin/workbench-data.js:1317` calls `GET /api/admin/products/${editId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/products/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/products/category-counts (public/admin/workbench-data.js:1395)
`public/admin/workbench-data.js:1395` calls `GET /api/admin/products/category-counts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/products/category-counts` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/products/stats (public/admin/workbench-data.js:1251)
`public/admin/workbench-data.js:1251` calls `GET /api/admin/products/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/products/stats` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/query-analysis (public/admin/workbench-data.js:342)
`public/admin/workbench-data.js:342` calls `GET /api/admin/query-analysis` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/query-analysis` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/reflections?limit=10 (public/admin/workbench-data.js:580)
`public/admin/workbench-data.js:580` calls `GET /api/admin/reflections?limit=10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/reflections` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/regression-cases (public/admin/workbench-data.js:630)
`public/admin/workbench-data.js:630` calls `GET /api/admin/regression-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/regression-cases` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/staff/stats (public/admin/workbench-data.js:419)
`public/admin/workbench-data.js:419` calls `GET /api/admin/staff/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff/stats` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/stats (public/admin/workbench-data.js:114)
`public/admin/workbench-data.js:114` calls `GET /api/admin/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/stats` 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/stats (public/admin/workbench-data.js:1546)
`public/admin/workbench-data.js:1546` calls `GET /api/admin/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/stats` 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/user-profiles (public/admin/workbench-data.js:460)
`public/admin/workbench-data.js:460` calls `GET /api/admin/user-profiles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/user-profiles` 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: GET /api/admin/users (public/admin/workbench-data.js:478)
`public/admin/workbench-data.js:478` calls `GET /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` 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/auth/me (public/js/app.js:1101)
`public/js/app.js:1101` calls `GET /api/auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/me` 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/harness/roles (public/admin/workbench-data.js:41)
`public/admin/workbench-data.js:41` calls `GET /api/harness/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/harness/roles` 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/harness/skills/grouped (public/admin/workbench-data.js:4)
`public/admin/workbench-data.js:4` calls `GET /api/harness/skills/grouped` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/harness/skills/grouped` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/leai/auth (public/js/app.js:2999)
`public/js/app.js:2999` calls `GET /api/leai/auth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/leai/auth` 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/lenovo/support/articles (public/admin/workbench-data.js:1701)
`public/admin/workbench-data.js:1701` calls `GET /api/lenovo/support/articles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/lenovo/support/articles` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/lenovo/support/drivers?keyword=${encodeURIComponent(kw)} (public/admin/workbench-data.js:1726)
`public/admin/workbench-data.js:1726` calls `GET /api/lenovo/support/drivers?keyword=${encodeURIComponent(kw)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/lenovo/support/drivers` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/lenovo/user/order/list (public/admin/workbench-data.js:1746)
`public/admin/workbench-data.js:1746` calls `GET /api/lenovo/user/order/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/lenovo/user/order/list` 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 /api/pipeline/classify/rules/status (public/admin/workbench-ai.js:1017)
`public/admin/workbench-ai.js:1017` calls `GET /api/pipeline/classify/rules/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/classify/rules/status` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/pipeline/pipeline/status (public/admin/workbench-pipeline.js:1894)
`public/admin/workbench-pipeline.js:1894` calls `GET /api/pipeline/pipeline/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/pipeline/status` 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/pipeline/pipeline/status (public/admin/workbench-pipeline.js:1977)
`public/admin/workbench-pipeline.js:1977` calls `GET /api/pipeline/pipeline/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/pipeline/status` 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/pipeline/stats/history (public/admin/workbench-pipeline.js:1816)
`public/admin/workbench-pipeline.js:1816` calls `GET /api/pipeline/stats/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/stats/history` 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 /api/pipeline/stats/history (public/admin/workbench-pipeline.js:1872)
`public/admin/workbench-pipeline.js:1872` calls `GET /api/pipeline/stats/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/stats/history` 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 /api/pipeline/stats/history (public/admin/workbench-pipeline.js:815)
`public/admin/workbench-pipeline.js:815` calls `GET /api/pipeline/stats/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/stats/history` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/product/${encodeURIComponent(sku)}/detail-images (public/js/app.js:95)
`public/js/app.js:95` calls `GET /api/product/${encodeURIComponent(sku)}/detail-images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/product/<p>/detail-images` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stores/geocode?address=${encodeURIComponent(address)} (public/admin/workbench-data.js:1772)
`public/admin/workbench-data.js:1772` calls `GET /api/stores/geocode?address=${encodeURIComponent(address)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stores/geocode` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stores/geocode?address=${encodeURIComponent(address)} (public/js/app.js:2645)
`public/js/app.js:2645` calls `GET /api/stores/geocode?address=${encodeURIComponent(address)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stores/geocode` 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/stores/nearby?lat=${encodeURIComponent(geo.lat)}&lng=${encodeURIComponent(geo.lng)} (public/js/app.js:2647)
`public/js/app.js:2647` calls `GET /api/stores/nearby?lat=${encodeURIComponent(geo.lat)}&lng=${encodeURIComponent(geo.lng)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stores/nearby` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stores/nearby?lat=${geo.lat}&lng=${geo.lng} (public/admin/workbench-data.js:1776)
`public/admin/workbench-data.js:1776` calls `GET /api/stores/nearby?lat=${geo.lat}&lng=${geo.lng}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stores/nearby` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /health (public/admin/workbench-data.js:72)
`public/admin/workbench-data.js:72` calls `GET /health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/health` 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 /health (public/admin/workbench-pipeline.js:1867)
`public/admin/workbench-pipeline.js:1867` calls `GET /health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/health` 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: PATCH /api/admin/skills/${name} (public/admin/workbench-data.js:32)
`public/admin/workbench-data.js:32` calls `PATCH /api/admin/skills/${name}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/skills/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /aiadmin/proxy/new/smart/touch/transformer/list (public/admin/workbench-data.js:2037)
`public/admin/workbench-data.js:2037` calls `POST /aiadmin/proxy/new/smart/touch/transformer/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/aiadmin/proxy/new/smart/touch/transformer/list` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/backup (public/admin/workbench-data.js:1679)
`public/admin/workbench-data.js:1679` calls `POST /api/admin/backup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/backup` 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/experiments (public/admin/workbench-data.js:1666)
`public/admin/workbench-data.js:1666` calls `POST /api/admin/experiments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/experiments` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/manual-qa (public/admin/workbench-data.js:206)
`public/admin/workbench-data.js:206` calls `POST /api/admin/manual-qa` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/manual-qa` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/metrics/collect (public/admin/workbench-data.js:572)
`public/admin/workbench-data.js:572` calls `POST /api/admin/metrics/collect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/metrics/collect` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/pages (public/admin/workbench-data.js:1035)
`public/admin/workbench-data.js:1035` calls `POST /api/admin/pages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/pages` 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/personas (public/admin/workbench-data.js:529)
`public/admin/workbench-data.js:529` calls `POST /api/admin/personas` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/personas` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/product-categories (public/admin/workbench-data.js:1415)
`public/admin/workbench-data.js:1415` calls `POST /api/admin/product-categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/product-categories` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/regression-cases (public/admin/workbench-data.js:646)
`public/admin/workbench-data.js:646` calls `POST /api/admin/regression-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/regression-cases` 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: POST /api/admin/regression-cases/run (public/admin/workbench-data.js:656)
`public/admin/workbench-data.js:656` calls `POST /api/admin/regression-cases/run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/regression-cases/run` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/restart (public/admin/workbench-data.js:1688)
`public/admin/workbench-data.js:1688` calls `POST /api/admin/restart` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/restart` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/run-evolution (public/admin/workbench-data.js:619)
`public/admin/workbench-data.js:619` calls `POST /api/admin/run-evolution` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/run-evolution` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/run-learning (public/admin/workbench-data.js:623)
`public/admin/workbench-data.js:623` calls `POST /api/admin/run-learning` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/run-learning` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users (public/admin/workbench-data.js:492)
`public/admin/workbench-data.js:492` calls `POST /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` 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/auth/login (public/js/app.js:1143)
`public/js/app.js:1143` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/login` 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/auth/logout (public/js/app.js:1155)
`public/js/app.js:1155` calls `POST /api/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/logout` 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/auth/send-code (public/js/app.js:1133)
`public/js/app.js:1133` calls `POST /api/auth/send-code` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/send-code` 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/chat/quick (public/js/app.js:3221)
`public/js/app.js:3221` calls `POST /api/chat/quick` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/quick` 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/chat/quick (public/js/app.js:752)
`public/js/app.js:752` calls `POST /api/chat/quick` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/quick` 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/chat/stream (public/js/app.js:1265)
`public/js/app.js:1265` calls `POST /api/chat/stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/stream` 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/chat/stream (public/js/app.js:4071)
`public/js/app.js:4071` calls `POST /api/chat/stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/stream` 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/chat/stream (public/js/fullscreen-chat.js:297)
`public/js/fullscreen-chat.js:297` calls `POST /api/chat/stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/stream` 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/geo-dashboard/sites (public/admin/workbench-geo.js:505)
`public/admin/workbench-geo.js:505` calls `POST /api/geo-dashboard/sites` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/geo-dashboard/sites` 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 /api/geo-dashboard/sites (public/admin/workbench-geo.js:853)
`public/admin/workbench-geo.js:853` calls `POST /api/geo-dashboard/sites` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/geo-dashboard/sites` 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 /api/geo-dashboard/summary (public/admin/workbench-geo.js:1293)
`public/admin/workbench-geo.js:1293` calls `POST /api/geo-dashboard/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/geo-dashboard/summary` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/harness/chat (public/admin/workbench-ai.js:1273)
`public/admin/workbench-ai.js:1273` calls `POST /api/harness/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/harness/chat` 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/harness/chat (public/admin/workbench-data.js:1086)
`public/admin/workbench-data.js:1086` calls `POST /api/harness/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/harness/chat` 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/harness/chat (public/admin/workbench-data.js:395)
`public/admin/workbench-data.js:395` calls `POST /api/harness/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/harness/chat` 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/harness/upload (public/admin/workbench-ai.js:1138)
`public/admin/workbench-ai.js:1138` calls `POST /api/harness/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/harness/upload` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/knowledge/upload (public/admin/workbench-data.js:180)
`public/admin/workbench-data.js:180` calls `POST /api/knowledge/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/knowledge/upload` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/leai/chat (public/js/app.js:3006)
`public/js/app.js:3006` calls `POST /api/leai/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/leai/chat` 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/pipeline/classify (public/admin/workbench-pipeline.js:1261)
`public/admin/workbench-pipeline.js:1261` calls `POST /api/pipeline/classify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/classify` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/pipeline/filter (public/admin/workbench-pipeline.js:1844)
`public/admin/workbench-pipeline.js:1844` calls `POST /api/pipeline/filter` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/filter` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/pipeline/stats (public/admin/workbench-pipeline.js:1791)
`public/admin/workbench-pipeline.js:1791` calls `POST /api/pipeline/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/stats` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/gen_qa.js:11)
`scripts/gen_qa.js:11` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/completions…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/gen_qa_full.js:13)
`scripts/gen_qa_full.js:13` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/comple…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/gen_qa_v2.js:167)
`scripts/gen_qa_v2.js:167` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/complet…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/ocr_image_docs.js:20)
`scripts/ocr_image_docs.js:20` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/com…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/ocr_image_docs.js:66)
`scripts/ocr_image_docs.js:66` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/com…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/ocr_test.js:18)
`scripts/ocr_test.js:18` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/completio…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/ocr_test.js:50)
`scripts/ocr_test.js:50` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/completio…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/regen_qa_guides.js:72)
`scripts/regen_qa_guides.js:72` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/co…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions (scripts/test_qa_v2.js:99)
`scripts/test_qa_v2.js:99` calls `POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/dashscope.aliyuncs.com/compatible-mode/v1/chat/complet…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal (scripts/weekly_refresh.js:68)
`scripts/weekly_refresh.js:68` calls `POST https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/open.feishu.cn/open-apis/auth/v3/tenant_access_…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://open.feishu.cn/open-apis/im/v1/messages?receive_id_type=${rcvType} (scripts/weekly_refresh.js:75)
`scripts/weekly_refresh.js:75` calls `POST https://open.feishu.cn/open-apis/im/v1/messages?receive_id_type=${rcvType}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/open.feishu.cn/open-apis/im/v1/messages` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/bot-config (public/admin/workbench-data.js:1213)
`public/admin/workbench-data.js:1213` calls `PUT /api/admin/bot-config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-config` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/experiments/${id}/status (public/admin/workbench-data.js:1635)
`public/admin/workbench-data.js:1635` calls `PUT /api/admin/experiments/${id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/experiments/<p>/status` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/marketing-tasks/${id}/execute (public/admin/workbench-data.js:1530)
`public/admin/workbench-data.js:1530` calls `PUT /api/admin/marketing-tasks/${id}/execute` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/marketing-tasks/<p>/execute` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/personas/${id}/activate (public/admin/workbench-data.js:534)
`public/admin/workbench-data.js:534` calls `PUT /api/admin/personas/${id}/activate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/personas/<p>/activate` If this points at an external API, prefix it with `http…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/compressor.js: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 — core/memory.js:44
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 — core/profiler.js: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 — knowledge/ingest.js:85
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 — public/admin/workbench-ai.js:955
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 — public/admin/workbench-data.js:1395
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 — public/admin/workbench-geo.js:197
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 — public/js/app.js:1133
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/crawl_biz.js:17
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/gen_qa.js:11
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/gen_qa_claude.js: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/gen_qa_full.js:13
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/gen_qa_v2.js:167
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/import_from_openapi.js: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 — scripts/ocr_image_docs.js:20
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/ocr_test.js: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 — scripts/regen_qa_guides.js:72
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/weekly_refresh.js: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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lenovo-leai-pc-design/references/component-patterns.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lenovo-leai-pc-design/references/component-patterns.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lenovo-leai-pc-design/references/fullscreen-dialog-framework.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lenovo-leai-pc-design/references/fullscreen-dialog-framework.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lenovo-leai-pc-design/references/layout-rules.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lenovo-leai-pc-design/references/layout-rules.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lenovo-leai-pc-design/references/pc-design-system.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lenovo-leai-pc-design/references/pc-design-system.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lenovo-leai-pc-design/references/real-pc-dialog-states.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lenovo-leai-pc-design/references/real-pc-dialog-states.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lexiang-ai-flow/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lexiang-ai-flow/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lexiang-deploy/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lexiang-deploy/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lexiang-dev/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/lexiang-dev/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: AGENTS.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.
AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, operator-readme. 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. 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 'direct_innerhtml_assignment' in docs/guan-jthl.html:186
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/guan-jthl.html:186 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/index-legacy.html:804
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/index-legacy.html:804 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/ops-lite.html:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/ops-lite.html:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-ai.js:108
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-ai.js:108 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-data.js:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-data.js:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-employee.js:15
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-employee.js:15 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-geo.js:156
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-geo.js:156 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-ops.js:645
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-ops.js:645 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-pages.js:6
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-pages.js:6 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-pipeline.js:638
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-pipeline.js:638 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-quality.js:528
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-quality.js:528 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-report.js:215
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-report.js:215 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench-v1.html:1720
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench-v1.html:1720 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/workbench.html:471
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/workbench.html:471 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/changelog.html:150
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/changelog.html:150 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/app.js:75
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/app.js:75 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/fullscreen-chat.js:236
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/fullscreen-chat.js:236 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/portal.js:172
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/portal.js:172 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in public/admin/index-legacy.html:2838
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
public/admin/index-legacy.html:2838 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in public/admin/workbench-data.js:244
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
public/admin/workbench-data.js:244 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in docs/guan-jthl.html:144
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
docs/guan-jthl.html:144 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/admin/index-legacy.html:3943
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/admin/index-legacy.html:3943 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/admin/workbench-data.js:1349
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/admin/workbench-data.js:1349 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/admin/workbench-geo.js:1634
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/admin/workbench-geo.js:1634 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/js/app.js:254
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/js/app.js:254 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/js/fullscreen-chat.js:344
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/js/fullscreen-chat.js:344 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in core/version.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
core/version.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in routes/admin.js:699
Found a known-risky pattern (node_child_process). Review and replace if possible.
routes/admin.js:699 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in routes/pipeline.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
routes/pipeline.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in routes/webhook.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
routes/webhook.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/auto-changelog.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/auto-changelog.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/weekly_refresh.js:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/weekly_refresh.js:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in skills/lexiang_classify.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
skills/lexiang_classify.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in skills/lexiang_filter.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
skills/lexiang_filter.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in skills/lexiang_intent.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
skills/lexiang_intent.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in skills/lexiang_pipeline.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
skills/lexiang_pipeline.js:2 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 111 placeholder/mock markers across 22 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 143 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 312 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 security security conf 1.00 Insecure pattern 'document_write' in public/admin/workbench.html:17
Found a known-risky pattern (document_write). Review and replace if possible.
public/admin/workbench.html:17 Document write
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/enrich_brand_news.py:extract_body, scripts/crawl_brand_full.py:extract_body 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.
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 Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `deleteOld` in scripts/gen_qa.js:49
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 `deleteOld` in scripts/gen_qa_claude.js:75
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 `deleteOld` in scripts/gen_qa_full.js:66
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 `fuzzyOld` in skills/pipeline_update_rules.js:70
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 `navOld` in routes/product_detail_images.js:32
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 `从gen_qa_v2` in scripts/test_qa_v2.js:6
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_and_extract
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/enrich_brand_news.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_article_content
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/crawl_brand_full.py:75
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_page
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/crawl_brand_news.py:12
low System graph software Dead code conf 1.00 Possibly dead Python function: is_price_disclosed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/gen_wiki_full.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
public/admin/local-preview-server.py:111
low System graph software Dead code conf 1.00 Possibly dead Python function: replacer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/gen_wiki_full.py:720
low System graph software Dead code conf 1.00 Possibly dead Python function: translate_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
public/admin/local-preview-server.py:82
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 — core/agent.js:666
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 — core/compressor.js:130
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 — core/dispatcher.js:34
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 — core/evolver.js:94
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 — core/experience.js:83
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 — core/learner.js:128
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 — core/memory.js:125
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 — core/monitor.js:99
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 — core/profiler.js:96
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 — core/skill-registry.js:30
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 — core/sms.js:59
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 — db/schema.js:368
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 — knowledge/brand_crawl.js:95
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 — knowledge/build_vectors.js:16
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 — knowledge/deduplicator.js:163
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 — knowledge/graph_rag.js:199
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 — knowledge/news_crawler.js:108
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 — knowledge/search.js:20
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 — knowledge/vector_index.js:42
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 — public/admin/workbench-employee.js:543
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 — routes/admin.js:548
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 — routes/auth.js:138
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 — routes/harness.js:80
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 — routes/pipeline.js:440
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 — routes/webhook.js:56
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 — scripts/backfill_links.js:86
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 — scripts/crawl_biz.js:163
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 — scripts/crawl_biz_playwright.js:136
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 — scripts/crawl_item_pages.js:95
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 — scripts/fix_short_batch.js:36
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 — scripts/gen_qa.js: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 — scripts/gen_qa_claude.js:89
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 — scripts/gen_qa_full.js:81
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 — scripts/gen_qa_v2.js:214
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 — scripts/import_excel_products.js:105
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 — scripts/import_from_openapi.js:113
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 — scripts/ocr_image_docs.js:103
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 — scripts/ocr_test.js:101
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 — scripts/pointer_eval.js:38
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 — scripts/rechunk_updated.js:22
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 — scripts/regen_qa_guides.js:131
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 — scripts/test_qa_v2.js:92
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 — scripts/token-stats.js:34
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 — scripts/weekly_refresh.js:14
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 — server.js:524
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 — skills/code_runner.js:14
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 /roles/:id
`routes/harness.js` declares `DELETE /roles/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`routes/knowledge.js` 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 /*path
`server.js` 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: GET /:id
`routes/knowledge.js` declares `GET /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:sku/detail-images
`routes/product_detail_images.js` declares `GET /:sku/detail-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: GET /admin
`server.js` declares `GET /admin` 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 /admin/*path
`server.js` declares `GET /admin/*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: GET /api/config/seckill
`server.js` declares `GET /api/config/seckill` 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/preview
`server.js` declares `GET /api/preview` 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/resolve-link
`server.js` declares `GET /api/resolve-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: GET /menu
`routes/harness.js` declares `GET /menu` 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 /public-search
`routes/knowledge.js` declares `GET /public-search` 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 /roles
`routes/harness.js` declares `GET /roles` 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 /schema/:name
`routes/harness.js` declares `GET /schema/:name` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /share/:token
`server.js` declares `GET /share/:token` 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 /skills
`routes/harness.js` declares `GET /skills` 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 /skills/grouped
`routes/harness.js` declares `GET /skills/grouped` 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 /sse/connect
`routes/harness.js` declares `GET /sse/connect` 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 /sse/heartbeat
`routes/harness.js` declares `GET /sse/heartbeat` 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 /user-roles/:userId
`routes/harness.js` declares `GET /user-roles/:userId` 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 /
`routes/log.js` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/login
`server.js` 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 /chat
`routes/harness.js` declares `POST /chat` 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 /crawl
`routes/knowledge.js` declares `POST /crawl` 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 /invoke
`routes/harness.js` declares `POST /invoke` 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 /roles
`routes/harness.js` declares `POST /roles` 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 /sse/say
`routes/harness.js` declares `POST /sse/say` 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 /text
`routes/knowledge.js` declares `POST /text` 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 /upload
`routes/harness.js` declares `POST /upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /url
`routes/knowledge.js` declares `POST /url` 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: PUT /roles/:id
`routes/harness.js` declares `PUT /roles/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /user-roles/:userId
`routes/harness.js` declares `PUT /user-roles/:userId` 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 /
`server.js` declares `USE /` 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/admin
`server.js` declares `USE /api/admin` 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/auth
`server.js` declares `USE /api/auth` 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/chat
`server.js` declares `USE /api/chat` 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/geo-dashboard
`server.js` declares `USE /api/geo-dashboard` 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/harness
`server.js` declares `USE /api/harness` 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/knowledge
`server.js` declares `USE /api/knowledge` 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/leai
`server.js` declares `USE /api/leai` 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/lenovo
`server.js` declares `USE /api/lenovo` 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/log
`server.js` declares `USE /api/log` 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/pipeline
`server.js` declares `USE /api/pipeline` 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/pointer
`server.js` declares `USE /api/pointer` 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/product
`server.js` declares `USE /api/product` 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/site
`server.js` declares `USE /api/site` 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/stores
`server.js` declares `USE /api/stores` 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/supplier
`server.js` declares `USE /api/supplier` 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/uploader
`server.js` declares `USE /api/uploader` 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/webhook
`server.js` declares `USE /api/webhook` 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: public/admin/workbench-ai.js (1530 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/admin/workbench-data.js (2158 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/admin/workbench-geo.js (1640 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/admin/workbench-pages.js (3318 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/admin/workbench-pipeline.js (2022 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/app.js (4240 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.

Showing first 300 of 302. Refine filters or use the findings page for deep search.

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/ce3ddbe8-dbc6-48f8-93b4-f0b5b6382a05/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ce3ddbe8-dbc6-48f8-93b4-f0b5b6382a05/

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.