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.

Systemsaholic/nexaas

https://github.com/Systemsaholic/nexaas · scanned 2026-06-16 00:27 UTC (2 months, 2 weeks ago)

289 raw signals (147 security + 142 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 142 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 15 Medium 40 Low 67 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 142 Crowd 0 Layer: Quality 62 Security 24 Frontend 38 Cicd 1 Api 26

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.

Commented-out code 24 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/`.

12 matching findings on this repo

info Commented-code block (5 lines) in mcp/servers/webstudio/src/safe-path.ts:44
info Commented-code block (5 lines) in scripts/test-concurrency-groups.mjs:5
info Commented-code block (5 lines) in scripts/test-shadow-drawer-124.mjs:149
info Commented-code block (5 lines) in packages/cli/src/conformance.ts:170
info Commented-code block (5 lines) in packages/cli/src/init.ts:177
info Commented-code block (8 lines) in packages/cli/src/migrations.ts:70
info Commented-code block (5 lines) in packages/cli/src/register-skill.ts:356
info Commented-code block (8 lines) in packages/palace/src/wal.ts:29
info Commented-code block (5 lines) in packages/palace/src/palace.ts:214
info Commented-code block (5 lines) in packages/palace/src/db.ts:18
info Commented-code block (5 lines) in packages/runtime/src/ai-skill-framework-tools…
info Commented-code block (5 lines) in packages/runtime/src/ai-skill.ts:241

View all commented-out code findings →

Config drift 4 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.

4 matching findings on this repo

low Stray `console.log` in TS/JS — packages/cli/src/config.ts:40
medium Insecure pattern 'node_child_process' in packages/cli/src/config.ts:13 packages/cli/src/config.ts:13
medium Runtime service client appears to use placeholder configuration
high Dangling fetch: POST https://api.telegram.org/bot${config.telegram.botToken}/se…

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/2c598bbd-1219-4e29-b5f9-98ba65f25388/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2c598bbd-1219-4e29-b5f9-98ba65f25388/

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.