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.

w2444866290-dev/clawbot

https://github.com/w2444866290-dev/clawbot · scanned 2026-06-16 00:53 UTC (2 months, 1 week ago)

24 raw signals (0 security + 24 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 17 actionable findings from 1 signal source. 7 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 17 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 7 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 17 Crowd 0 Layer: Frontend 3 Security 3 Cicd 1 Quality 10

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 72.1/100 with 88.9% coverage. It contains 644 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 24 findings — concentrated in quality (17), frontend (3), security (3). Risk profile is low: 0 critical, 0 high, 7 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 15 of 17 actionable findings. 24 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/clawd-emotes/references/prop-recipes.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/clawd-emotes/references/prop-recipes.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in assets/avatar/clawbot-emotes.html:216

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

assets/avatar/clawbot-emotes.html:216 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in .claude/skills/clawd-emotes/scripts/export_gif.js:35

Found a known-risky pattern (node_child_process). Review and replace if possible.

.claude/skills/clawd-emotes/scripts/export_gif.js:35 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in .claude/skills/clawd-emotes/scripts/export_transparent.js:8

Found a known-risky pattern (node_child_process). Review and replace if possible.

.claude/skills/clawd-emotes/scripts/export_transparent.js:8 Node child process

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — clawbot/approval.py:153

`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `CHROME`, `CLAWBOT_APPROVAL_TIMEOUT`, `CLAWBOT_APPROVAL_TOKEN`, `CLAWBOT_APPROVAL_URL`, `CLAWBOT_READER_OPEN_ID`, `CLAWBOT_READER_TOKEN`, `CLAWBOT_READER_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 22 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: clawbot/approval_mcp.py:handle, clawbot/reader_mcp.py:handle This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.

5 occurrences

repo-level (5 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: clawbot/sender.py:send_card, clawbot/sender.py:send_card, clawbot/sender.py:send_card This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.

4 occurrences

repo-level (4 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `receive_v1` in clawbot/gateway.py:45

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — .claude/skills/clawd-emotes/scripts/export_gif.js:101

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — .claude/skills/clawd-emotes/scripts/export_transparent.js:65

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

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/4da73a2b-ff5b-48c7-b8bc-bf12ee7434f1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4da73a2b-ff5b-48c7-b8bc-bf12ee7434f1/

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.