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.

rezprotocol/rez-chat

https://github.com/rezprotocol/rez-chat · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

134 raw signals (4 security + 130 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 3 findings
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.
3 matching findings on this repo
  • low Old/deprecated-named symbol `hasLegacy` in src/ui/services/auth/AccountAuthServ…
  • low Old/deprecated-named symbol `_keystoreStoreLegacy` in src/ui/services/auth/Auth…
  • low Old/deprecated-named symbol `selectedIsLegacy` in src/ui/views/LoginUnlockView.…
View all legacy markers findings →
Commented-out code 85 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 (7 lines) in electron/main.mjs:48
  • info Commented-code block (7 lines) in electron/runtime/BiometricGate.mjs:73
  • info Commented-code block (7 lines) in test/chat-server.identity.bip39.test.js:3
  • info Commented-code block (5 lines) in test/server.peerlink.protocol.handshake.test.…
  • info Commented-code block (7 lines) in test/server.group-message-defer.test.js:1
  • info Commented-code block (7 lines) in test/server.inbound-pipeline.ordering.e2e.tes…
  • info Commented-code block (5 lines) in test/server.group-ops-propagation.test.js:422
  • info Commented-code block (5 lines) in test/server.member-contact-op.test.js:129
  • info Commented-code block (7 lines) in test/architecture.views-strict.test.js:26
  • info Commented-code block (5 lines) in test/server.invites.accept.test.js:188
  • info Commented-code block (7 lines) in test/peerlink.commit-convergence.test.js:20
  • info Commented-code block (6 lines) in test/server.peerlink.recovery.test.js:1
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • info Commented-code block (6 lines) in src/server/config/defaultRezConfig.js:25
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/fcc8d935-01ec-45bb-9ee7-ab39bc83e1dc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fcc8d935-01ec-45bb-9ee7-ab39bc83e1dc/

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.