ucsandman/DashClaw

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.

153 of your 364 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.48s · analysis 46.21s · 17.6 MB · GitHub API rate-limit (preflight)

https://github.com/ucsandman/DashClaw · scanned 2026-06-05 16:58 UTC (5 days ago) · 10 languages

1158 raw signals (336 security + 822 graph) 29th percentile · Javascript · large (100-500K LoC) System graph score 77 (lower by 12)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days ago · v2 · 521 actionable findings from 2 signal sources. 226 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 · 369 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	0.0	0.25	0.00
`testing_score`	90.0	0.20	18.00
`documentation_score`	96.8	0.15	14.52
`practices_score`	100.0	0.15	15.00
`code_quality`	46.0	0.10	4.60
Overall		1.00	64.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 60 Medium 76 Low 155 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 152 System graph 369 Crowd 0 Layer: Quality 256 Security 47 Software 99 Cicd 11 Api 1 Frontend 105 Hardware 2

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 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:511
low Very large file: sdk/legacy/dashclaw-v1.js (2945 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.js:10
low Old/deprecated-named symbol `showLegacy` in app/docs/page.js:202
low Old/deprecated-named symbol `showLegacy` in app/docs/DocsSidebarClient.js:15
low Old/deprecated-named symbol `showLegacy` in app/components/CopyMarkdownButton.j…
low Old/deprecated-named symbol `getCapabilityHealthSummaryLegacy` in app/lib/capab…
medium `fetch()` without try/.catch or AbortSignal — sdk/legacy/dashclaw-v1.js:150

View all legacy markers findings →

Commented-out code 108 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:46
info Commented-code block (5 lines) in vitest.config.js:11
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 (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:77
info Commented-code block (5 lines) in __tests__/unit/integrity-canonicalize.test.js…
info Commented-code block (5 lines) in __tests__/unit/connect-complete-discord-alert…
info Commented-code block (5 lines) in __tests__/unit/session-detail.page.test.jsx:5
info Commented-code block (5 lines) in __tests__/unit/workflow-resume.route.test.js:4

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 File has no detected symbols: playwright.config.js
low File has no detected symbols: tailwind.config.js
low File has no detected symbols: vitest.config.js
low File has no detected symbols: postcss.config.js
low File has no detected symbols: drizzle.config.js
low Stray `console.log` in TS/JS — cli/lib/config.js:122
info Commented-code block (5 lines) in vitest.config.js:11
medium `fetch()` without try/.catch or AbortSignal — app/policies/components/ShieldCon…

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/d3c22f64-81c6-4c3d-aaa5-f34a57f8b76b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d3c22f64-81c6-4c3d-aaa5-f34a57f8b76b/

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.