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.

boggspa/TaskWraith

https://github.com/boggspa/TaskWraith · scanned 2026-06-17 01:42 UTC (1 month, 1 week ago)

265 raw signals (0 security + 265 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 265 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 5 Medium 58 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 265 Crowd 0 Layer: Frontend 12 Security 49 Cicd 2 Quality 202

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 2 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.

2 matching findings on this repo

low Old/deprecated-named symbol `nextLegacy` in src/main/index.ts:15040
low Old/deprecated-named symbol `sixParticipantLegacy` in src/main/EnsemblePrompt.t…

View all legacy markers findings →

Commented-out code 157 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.vite.config.ts:13
info Commented-code block (5 lines) in tests/fake-iphone/e2e.trusted-reconnect.test.…
info Commented-code block (5 lines) in scripts/spike-grok-acp.cjs:7
info Commented-code block (9 lines) in scripts/smoke-packaged-electron.cjs:171
info Commented-code block (10 lines) in relay/src/server.ts:130
info Commented-code block (5 lines) in src/main/BridgeDaemonClient.ts:124
info Commented-code block (9 lines) in src/main/index.ts:909
info Commented-code block (5 lines) in src/main/KimiWireExitDecision.test.ts:20
info Commented-code block (6 lines) in src/main/EnsemblePrompt.ts:47
info Commented-code block (5 lines) in src/main/TaskWraithMcpTools.ts:62
info Commented-code block (6 lines) in src/main/geminiMcpConstants.ts:5
info Commented-code block (11 lines) in src/main/ProviderQuotaSnapshots.ts:193

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

info Commented-code block (7 lines) in electron.vite.config.ts:13
info Commented-code block (8 lines) in src/main/cursor/CursorWorkspaceConfig.ts:3

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/a6ed76dd-8c79-4d48-b298-2765f7b265b0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a6ed76dd-8c79-4d48-b298-2765f7b265b0/

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.