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

cindiekinzz-coder/NESTstack

https://github.com/cindiekinzz-coder/NESTstack · scanned 2026-06-17 01:49 UTC (1 month, 1 week ago)

198 raw signals (0 security + 198 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -13.2 (diff) · 198 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

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

critical System graph security Secrets conf 1.00 Possible secret in dashboard/src/js/shadow-api.js
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
dashboard/src/js/shadow-api.js:8
high System graph api Wiring conf 1.00 Dangling fetch: GET /guilds/${guildId}/channels (NEST-discord/worker/discord.ts:152)
`NEST-discord/worker/discord.ts:152` calls `GET /guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/guilds/<p>/channels` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /guilds/${guildId}/channels (NESTeq/workers/discord-mcp/src/discord.ts:152)
`NESTeq/workers/discord-mcp/src/discord.ts:152` calls `GET /guilds/${guildId}/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/guilds/<p>/channels` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /guilds/${guildId}?with_counts=true (NEST-discord/worker/discord.ts:148)
`NEST-discord/worker/discord.ts:148` calls `GET /guilds/${guildId}?with_counts=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/guilds/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /guilds/${guildId}?with_counts=true (NESTeq/workers/discord-mcp/src/discord.ts:148)
`NESTeq/workers/discord-mcp/src/discord.ts:148` calls `GET /guilds/${guildId}?with_counts=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/guilds/<p>` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /users/@me/guilds (NEST-discord/worker/discord.ts:144)
`NEST-discord/worker/discord.ts:144` calls `GET /users/@me/guilds` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/@me/guilds` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /users/@me/guilds (NESTeq/workers/discord-mcp/src/discord.ts:144)
`NESTeq/workers/discord-mcp/src/discord.ts:144` calls `GET /users/@me/guilds` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/@me/guilds` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.elevenlabs.io/v1/user (NESTdesktop/local-agent.js:220)
`NESTdesktop/local-agent.js:220` calls `GET https://api.elevenlabs.io/v1/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/user` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.spotify.com/v1${endpoint} (NESTeq/workers/ai-mind/src/spotify.ts:163)
`NESTeq/workers/ai-mind/src/spotify.ts:163` calls `GET https://api.spotify.com/v1${endpoint}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.spotify.com/v1/<p>` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.spotify.com/v1/me (NESTeq/workers/ai-mind/src/spotify.ts:172)
`NESTeq/workers/ai-mind/src/spotify.ts:172` calls `GET https://api.spotify.com/v1/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.spotify.com/v1/me` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://openrouter.ai/api/v1/... (NEST-gateway/src/openrouter.ts:4)
`NEST-gateway/src/openrouter.ts:4` calls `GET https://openrouter.ai/api/v1/...` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/openrouter.ai/api/v1/...` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://openrouter.ai/api/v1/models (NESTdesktop/local-agent.js:201)
`NESTdesktop/local-agent.js:201` calls `GET https://openrouter.ai/api/v1/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/openrouter.ai/api/v1/models` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://your-garmin-sync.workers.dev/status (dashboard/src/js/api.js:269)
`dashboard/src/js/api.js:269` calls `GET https://your-garmin-sync.workers.dev/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/your-garmin-sync.workers.dev/status` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://your-garmin-sync.workers.dev/status (NESTeq/dashboard/js/api.js:193)
`NESTeq/dashboard/js/api.js:193` calls `GET https://your-garmin-sync.workers.dev/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/your-garmin-sync.workers.dev/status` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /channels/${channelId}/messages (NEST-discord/worker/discord.ts:93)
`NEST-discord/worker/discord.ts:93` calls `POST /channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/<p>/messages` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /channels/${channelId}/messages (NESTeq/workers/discord-mcp/src/discord.ts:93)
`NESTeq/workers/discord-mcp/src/discord.ts:93` calls `POST /channels/${channelId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/<p>/messages` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST https://accounts.spotify.com/api/token (NESTeq/workers/ai-mind/src/spotify.ts:123)
`NESTeq/workers/ai-mind/src/spotify.ts:123` calls `POST https://accounts.spotify.com/api/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/accounts.spotify.com/api/token` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://accounts.spotify.com/api/token (NESTeq/workers/ai-mind/src/spotify.ts:57)
`NESTeq/workers/ai-mind/src/spotify.ts:57` calls `POST https://accounts.spotify.com/api/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/accounts.spotify.com/api/token` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/text-to-speech/${voiceId} (NEST-gateway/src/tts.ts:65)
`NEST-gateway/src/tts.ts:65` calls `POST https://api.elevenlabs.io/v1/text-to-speech/${voiceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/text-to-speech/<p>` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.tavily.com/search (NEST-gateway/src/tools/execute.ts:387)
`NEST-gateway/src/tools/execute.ts:387` calls `POST https://api.tavily.com/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.tavily.com/search` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.tavily.com/search (NESTdesktop/pc-tools/web.js:61)
`NESTdesktop/pc-tools/web.js:61` calls `POST https://api.tavily.com/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.tavily.com/search` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/chat.ts:435)
`NEST-gateway/src/chat.ts:435` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/chat.ts:516)
`NEST-gateway/src/chat.ts:516` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/daemon.ts:1181)
`NEST-gateway/src/daemon.ts:1181` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/daemon.ts:1502)
`NEST-gateway/src/daemon.ts:1502` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/daemon.ts:1554)
`NEST-gateway/src/daemon.ts:1554` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/daemon.ts:2119)
`NEST-gateway/src/daemon.ts:2119` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/daemon.ts:574)
`NEST-gateway/src/daemon.ts:574` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/daemon.ts:699)
`NEST-gateway/src/daemon.ts:699` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NEST-gateway/src/tools/execute.ts:251)
`NEST-gateway/src/tools/execute.ts:251` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NESTchat/chat-handler.example.ts:313)
`NESTchat/chat-handler.example.ts:313` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NESTchat/chat-handler.example.ts:393)
`NESTchat/chat-handler.example.ts:393` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://openrouter.ai/api/v1/chat/completions (NESTsoul/src/nestsoul-endpoints.ts:97)
`NESTsoul/src/nestsoul-endpoints.ts:97` calls `POST https://openrouter.ai/api/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:/openrouter.ai/api/v1/chat/completions` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /channels/${channelId}/messages/${messageId}/reactions/${encodedEmoji}/@me (NEST-discord/worker/discord.ts:135)
`NEST-discord/worker/discord.ts:135` calls `PUT /channels/${channelId}/messages/${messageId}/reactions/${encodedEmoji}/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/<p>/messages/<p>/reactions…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /channels/${channelId}/messages/${messageId}/reactions/${encodedEmoji}/@me (NESTeq/workers/discord-mcp/src/discord.ts:135)
`NESTeq/workers/discord-mcp/src/discord.ts:135` calls `PUT /channels/${channelId}/messages/${messageId}/reactions/${encodedEmoji}/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/<p>/messages/<p…
Dangling fetchHelper:request
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/src/js/api.js:61
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 — dashboard/src/js/chat.js:341
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 — dashboard/src/js/pc.js:116
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 — NEST-discord/src/toolList.ts:113
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 — NEST-discord/src/tools/channel.ts:27
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 — NEST-discord/src/tools/forum.ts: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 — NEST-discord/src/tools/reactions.ts:25
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 — NEST-discord/src/tools/send-message.ts:16
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — NEST-discord/src/tools/server.ts:21
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 — NEST-discord/src/tools/webhooks.ts:33
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 — NEST-discord/worker/discord.ts: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 — NEST-discord/worker/index.ts:135
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 — NEST-gateway/src/chat.ts:435
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 — NEST-gateway/src/daemon.ts:263
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 — NEST-gateway/src/index.ts:48
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 — NEST-gateway/src/openrouter.ts:4
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 — NEST-gateway/src/proxy.ts:77
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — NEST-gateway/src/tools/cloudflare.ts: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 — NEST-gateway/src/tools/discord.ts:18
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — NEST-gateway/src/tools/execute.ts:41
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 — NEST-gateway/src/tts.ts:65
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 — NESTchat/chat-handler.example.ts:313
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 — NESTdesktop/dashboard/js/chat.js:313
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 — NESTdesktop/dashboard/js/config.js:42
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 — NESTdesktop/dashboard/js/pc.js:116
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 — NESTdesktop/local-agent.js:408
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 — NESTeq/dashboard/js/api.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 — NESTeq/nexus-ingester/src/api.js:30
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — NESTeq/workers/ai-mind/src/index.ts:1283
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 — NESTeq/workers/ai-mind/src/spotify.ts:123
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 — NESTeq/workers/discord-mcp/src/discord.ts: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 — NESTeq/workers/discord-mcp/src/index.ts:135
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 — NESTeq/workers/garmin-sync/src/index.ts:128
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 — NESTeq/workers/rooms-worker/scripts/backfill.mjs:51
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 — NESTeq/workers/rooms-worker/src/index.ts:459
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 — NESTsoul/src/nestsoul-endpoints.ts:97
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci, tests, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NEST-discord/worker/index.ts:325
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NEST-discord/worker/index.ts:325 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NEST-gateway/src/chat.ts:327
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NEST-gateway/src/chat.ts:327 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NEST-gateway/src/daemon.ts:334
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NEST-gateway/src/daemon.ts:334 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NEST-gateway/src/index.ts:42
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NEST-gateway/src/index.ts:42 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NEST-gateway/src/mobile.ts:29
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NEST-gateway/src/mobile.ts:29 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NEST-gateway/src/tts.ts:9
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NEST-gateway/src/tts.ts:9 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTdesktop/dashboard/functions/api/chat/completions.js:14
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTdesktop/dashboard/functions/api/chat/completions.js:14 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTdesktop/dashboard/serve.js:59
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTdesktop/dashboard/serve.js:59 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTeq/workers/ai-mind/src/index.ts:1289
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTeq/workers/ai-mind/src/index.ts:1289 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTeq/workers/discord-mcp/src/index.ts:325
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTeq/workers/discord-mcp/src/index.ts:325 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTeq/workers/fox-mind/src/index.js:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTeq/workers/fox-mind/src/index.js:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTeq/workers/rooms-worker/src/index.ts:34
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTeq/workers/rooms-worker/src/index.ts:34 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in NESTsoul/src/nestsoul-endpoints.ts:24
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
NESTsoul/src/nestsoul-endpoints.ts:24 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/alex.html:779
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/alex.html:779 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/autonomous.html:466
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/autonomous.html:466 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/chat.html:233
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/chat.html:233 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/chats.html:342
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/chats.html:342 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/fox.html:559
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/fox.html:559 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/gallery.html:217
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/gallery.html:217 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/housekeeping.html:176
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/housekeeping.html:176 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/index.html:698
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/index.html:698 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/js/chat.js:182
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/js/chat.js:182 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/js/code.js:88
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/js/code.js:88 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/neural.html:419
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/neural.html:419 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/orb.html:473
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/orb.html:473 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/shadow.html:334
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/shadow.html:334 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/us.html:405
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/us.html:405 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/src/writing.html:348
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/src/writing.html:348 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/autonomous.html:466
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/autonomous.html:466 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/chat.html:256
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/chat.html:256 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/companion.html:779
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/companion.html:779 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/gallery.html:216
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/gallery.html:216 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/housekeeping.html:192
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/housekeeping.html:192 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/human.html:559
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/human.html:559 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/index.html:695
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/index.html:695 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/js/chat.js:191
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/js/chat.js:191 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/js/code.js:86
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/js/code.js:86 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/js/config.js:125
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/js/config.js:125 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/neural.html:419
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/neural.html:419 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/orb.html:473
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/orb.html:473 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/setup.html:404
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/setup.html:404 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/share/mind-health-card.html:268
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/share/mind-health-card.html:268 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/us.html:404
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/us.html:404 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/writing.html:348
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTdesktop/dashboard/writing.html:348 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTeq/dashboard/alex.html:487
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTeq/dashboard/alex.html:487 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTeq/dashboard/fox.html:439
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTeq/dashboard/fox.html:439 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTeq/dashboard/housekeeping.html:146
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTeq/dashboard/housekeeping.html:146 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTeq/dashboard/index.html:242
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTeq/dashboard/index.html:242 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTeq/dashboard/us.html:401
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTeq/dashboard/us.html:401 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in NESTsoul/dashboard/soul-tab.html:95
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
NESTsoul/dashboard/soul-tab.html:95 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in dashboard/src/autonomous.html:772
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
dashboard/src/autonomous.html:772 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in NESTdesktop/dashboard/autonomous.html:772
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
NESTdesktop/dashboard/autonomous.html:772 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in NESTdesktop/dashboard/setup.html:735
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
NESTdesktop/dashboard/setup.html:735 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTdesktop/pc-tools/app.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTdesktop/pc-tools/app.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTdesktop/pc-tools/clipboard.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTdesktop/pc-tools/clipboard.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTdesktop/pc-tools/grep.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTdesktop/pc-tools/grep.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTdesktop/pc-tools/process.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTdesktop/pc-tools/process.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTdesktop/pc-tools/screenshot.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTdesktop/pc-tools/screenshot.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTdesktop/pc-tools/shell.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTdesktop/pc-tools/shell.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in NESTeq/workers/rooms-worker/scripts/backfill.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
NESTeq/workers/rooms-worker/scripts/backfill.mjs:13 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 Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 155 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 105 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — dashboard/src/js/chat.js:441
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — dashboard/src/js/code.js:793
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — NESTdesktop/dashboard/js/chat.js:433
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — NESTdesktop/dashboard/js/code.js:791
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: NEST-discord/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
NEST-discord/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: NEST-gateway/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
NEST-gateway/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: NESTcode/nestcode-cli/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
NESTcode/nestcode-cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: NESTeq/workers/discord-mcp/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
NESTeq/workers/discord-mcp/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: NESTeq/workers/garmin-sync/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
NESTeq/workers/garmin-sync/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: NESTeq/workers/rooms-worker/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
NESTeq/workers/rooms-worker/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in NEST-gateway/src/tts.ts:73
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 `migrateLegacy` in NESTdesktop/local-agent.js:117
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — dashboard/src/js/code.js:711
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 — NESTcode/nestcode-cli/src/index.jsx:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — NESTdesktop/dashboard/js/chat.js:1339
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 — NESTdesktop/dashboard/js/code.js:709
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 — NESTdesktop/dashboard/serve.js:165
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 — NESTdesktop/local-agent.js:147
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 — NESTeq/nexus-ingester/scripts/extract-conversation.js:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — NESTeq/nexus-ingester/scripts/scan-chat-html.js:32
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 — NESTeq/nexus-ingester/src/index.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 — NESTeq/workers/garmin-sync/src/index.ts:177
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: ALL /api/{*path}
`NESTdesktop/local-agent.js` declares `ALL /api/{*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: ALL /mcp
`NEST-discord/src/transport.ts` declares `ALL /mcp` 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: ALL /v1/{*path}
`NESTdesktop/local-agent.js` declares `ALL /v1/{*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 /
`NESTdesktop/pc-tools/clipboard.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 /list
`NESTdesktop/pc-tools/app.js` declares `GET /list` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /screenshot
`NESTdesktop/pc-tools/screenshot.js` declares `GET /screenshot` 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 /
`NESTdesktop/pc-tools/clipboard.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 /chat/completions
`NESTdesktop/local-agent.js` declares `POST /chat/completions` 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 /edit
`NESTdesktop/pc-tools/file-edit.js` declares `POST /edit` 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 /fetch
`NESTdesktop/pc-tools/web.js` declares `POST /fetch` 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 /glob
`NESTdesktop/pc-tools/glob.js` declares `POST /glob` 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 /grep
`NESTdesktop/pc-tools/grep.js` declares `POST /grep` 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 /kill
`NESTdesktop/pc-tools/process.js` declares `POST /kill` 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 /launch
`NESTdesktop/pc-tools/app.js` declares `POST /launch` 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 /read
`NESTdesktop/pc-tools/file-read.js` declares `POST /read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /search
`NESTdesktop/pc-tools/web.js` declares `POST /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: POST /shell
`NESTdesktop/pc-tools/shell.js` declares `POST /shell` 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 /write
`NESTdesktop/pc-tools/file-write.js` declares `POST /write` 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 /
`NESTdesktop/pc-tools/index.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 /app
`NESTdesktop/pc-tools/index.js` declares `USE /app` 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 /clipboard
`NESTdesktop/pc-tools/index.js` declares `USE /clipboard` 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 /file
`NESTdesktop/pc-tools/index.js` declares `USE /file` 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 /pc
`NESTdesktop/local-agent.js` declares `USE /pc` 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 /process
`NESTdesktop/pc-tools/index.js` declares `USE /process` 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 /web
`NESTdesktop/pc-tools/index.js` declares `USE /web` 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: dashboard/src/js/code.js (1645 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: NEST-gateway/src/daemon.ts (2322 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: NESTdesktop/dashboard/js/chat.js (1457 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: NESTdesktop/dashboard/js/code.js (1619 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: NESTeq/workers/ai-mind/src/index.ts (2745 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/8bf21dda-ea24-4b7c-8e6d-5a91c3b4b45a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8bf21dda-ea24-4b7c-8e6d-5a91c3b4b45a/

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.