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.

RowitZou/lightclaw

https://github.com/RowitZou/lightclaw · scanned 2026-06-15 23:56 UTC (2 months, 3 weeks ago)

277 raw signals (0 security + 277 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 277 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 277 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 6 Medium 18 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 277 Crowd 0 Layer: Frontend 4 Network 1 Hardware 3 Security 11 Cicd 2 Quality 255 Api 1

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 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 `pickWithLegacy` in src/config.ts:609
low Old/deprecated-named symbol `tr_legacy` in src/taskrun/store.test.ts:706
low Old/deprecated-named symbol `pickWithLegacy` in src/identity/paths.ts:4

View all legacy markers findings →

Commented-out code 221 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 (6 lines) in scripts/smoke-feishu-task-card.ts:3
info Commented-code block (7 lines) in scripts/build-bundled-skills.ts:4
info Commented-code block (7 lines) in src/config.ts:456
info Commented-code block (5 lines) in src/api.ts:68
info Commented-code block (10 lines) in src/transient-error.ts:35
info Commented-code block (8 lines) in src/process-lock.ts:12
info Commented-code block (11 lines) in src/query-session-memory.test.ts:19
info Commented-code block (5 lines) in src/init.ts:93
info Commented-code block (13 lines) in src/messages.ts:96
info Commented-code block (10 lines) in src/query-empty-stop-backstop.test.ts:17
info Commented-code block (6 lines) in src/paths.ts:4
info Commented-code block (5 lines) in src/token-estimate.test.ts:115

View all commented-out code findings →

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

5 matching findings on this repo

low Very large file: src/config.ts (2209 lines)
low Old/deprecated-named symbol `pickWithLegacy` in src/config.ts:609
info Commented-code block (7 lines) in src/config.ts:456
info Commented-code block (7 lines) in src/config-file.ts:7
info Commented-code block (5 lines) in src/channels/config.ts:50

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/90ebbc3e-58fa-4c9e-9769-0f4b8d99fb0c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/90ebbc3e-58fa-4c9e-9769-0f4b8d99fb0c/

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.