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.

ucsandman/DashClaw

https://github.com/ucsandman/DashClaw · scanned 2026-06-16 03:50 UTC (2 months ago)

1219 raw signals (0 security + 1219 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v5 · last Δ +1.5 (diff) · 576 actionable findings from 1 signal source. 46 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 · 576 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 16 High 8 Medium 164 Low 113 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 576 Crowd 0 Layer: Software 21 Api 1 Frontend 114 Hardware 1 Security 72 Cicd 4 Quality 363

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 9 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.

9 matching findings on this repo

low Stray `console.log` in TS/JS — sdk/legacy/dashclaw-v1.js:526
low Very large file: sdk/legacy/dashclaw-v1.js (2960 lines)
low Old/deprecated-named symbol `act_test_legacy` in __tests__/unit/capability-heal…
low Old/deprecated-named symbol `includeLegacy` in app/api/docs/raw/route.ts:10
low Old/deprecated-named symbol `showLegacy` in app/docs/DocsSidebarClient.tsx:26
low Old/deprecated-named symbol `showLegacy` in app/docs/page.tsx:252
low Old/deprecated-named symbol `showLegacy` in app/components/CopyMarkdownButton.t…
low Old/deprecated-named symbol `getCapabilityHealthSummaryLegacy` in app/lib/capab…
medium `fetch()` without try/.catch or AbortSignal — sdk/legacy/dashclaw-v1.js:165

View all legacy markers findings →

Commented-out code 196 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 middleware.js:57
info Commented-code block (5 lines) in vitest.config.js:14
info Commented-code block (6 lines) in next.config.js:80
info Commented-code block (6 lines) in __tests__/integration/hosted/end-to-end.test.…
info Commented-code block (6 lines) in __tests__/unit/governance-panel.test.jsx:5
info Commented-code block (5 lines) in __tests__/unit/sessions-detail.route.test.js:4
info Commented-code block (5 lines) in __tests__/unit/middleware.test.js:54
info Commented-code block (6 lines) in __tests__/unit/actions-loops.route.test.js:4
info Commented-code block (5 lines) in __tests__/unit/compliance-page.test.jsx:5
info Commented-code block (6 lines) in __tests__/unit/mcp-tools.test.js:91
info Commented-code block (7 lines) in __tests__/unit/signals-intel.test.js:35
info Commented-code block (5 lines) in __tests__/unit/integrity-canonicalize.test.js…

View all commented-out code findings →

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

8 matching findings on this repo

low Stray `console.log` in TS/JS — cli/lib/config.js:148
critical Possible secret in __tests__/unit/cli-config-insecure-url.test.js __tests__/unit/cli-config-insecure-url.test.js:9
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/skills/dashclaw-agent/set… .claude/skills/dashclaw-agent/setup-dashclaw/SKIL…:39
high Agent instruction/config may expose a secret: .claude/skills/dashclaw-agent/ins… .claude/skills/dashclaw-agent/instrument-agent/SK…:188
high Agent instruction/config may expose a secret: .claude/skills/dashclaw-governanc… .claude/skills/dashclaw-governance/references/gov…:80
info Commented-code block (5 lines) in vitest.config.js:14
info Commented-code block (6 lines) in next.config.js:80

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/a3e22baf-4e2f-4326-91a6-006f2c15803e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a3e22baf-4e2f-4326-91a6-006f2c15803e/

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.