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.

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

100.0% cov · 198 findings

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

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `migrateLegacy` in NESTdesktop/local-agent.js:117

View all legacy markers findings →

Commented-out code 9 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

9 matching findings on this repo

info Commented-code block (6 lines) in NEST-gateway/src/index.ts:252
info Commented-code block (6 lines) in NESTeq/workers/ai-mind/src/ade.ts:28
info Commented-code block (5 lines) in NESTeq/nexus-ingester/src/parse-grok.js:7
info Commented-code block (5 lines) in NESTeq/nexus-ingester/src/index.js:152
info Commented-code block (16 lines) in NESTeq/nexus-ingester/src/parse-chatgpt.js:8
info Commented-code block (5 lines) in NESTeq/nexus-ingester/src/parse-claude-native…
info Commented-code block (5 lines) in NESTdesktop/local-agent.js:499
info Commented-code block (8 lines) in NESTdesktop/dashboard/js/chat.js:697
info Commented-code block (5 lines) in NESTchat/chat-handler.example.ts:235

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

medium Insecure pattern 'direct_innerhtml_assignment' in NESTdesktop/dashboard/js/conf… NESTdesktop/dashboard/js/config.js:125
medium `fetch()` without try/.catch or AbortSignal — NESTdesktop/dashboard/js/config.j…

View all config drift findings →

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.