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.

darkhtk/deskrelay

https://github.com/darkhtk/deskrelay · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

133 raw signals (0 security + 133 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 133 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 26 Low 68 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 133 Crowd 0 Layer: Frontend 11 Security 14 Quality 70 Api 38

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 `apr_legacy` in packages/site-frontend/test/approva…

View all legacy markers findings →

Commented-out code 38 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 packages/pc-connector-cli/src/cli.ts:290
info Commented-code block (5 lines) in packages/pc-connector-cli/src/bin.ts:12
info Commented-code block (5 lines) in packages/behavior-sdk/src/ipc.ts:4
info Commented-code block (6 lines) in packages/behavior-sdk/src/in-process-host.ts:1
info Commented-code block (7 lines) in packages/behavior-sdk/src/host.ts:3
info Commented-code block (5 lines) in packages/behavior-sdk/src/manifest-loader.ts:…
info Commented-code block (5 lines) in packages/behavior-sdk/src/runtime.ts:3
info Commented-code block (6 lines) in packages/behavior-sdk/test/spawn-argv.test.ts…
info Commented-code block (10 lines) in packages/behaviors/remote-claude/src/index.t…
info Commented-code block (5 lines) in packages/behaviors/remote-claude/src/session-…
info Commented-code block (10 lines) in packages/behaviors/remote-claude/src/claude-…
info Commented-code block (5 lines) in packages/behaviors/remote-claude/src/hooks/_s…

View all commented-out code 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/b8434bfe-682e-4c8a-9d48-7b49117daf4d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b8434bfe-682e-4c8a-9d48-7b49117daf4d/

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.