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.

chat4000/chat4000-openclaw-plugin

https://github.com/chat4000/chat4000-openclaw-plugin · scanned 2026-06-17 01:47 UTC (1 month, 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 1 month, 1 week ago · v2 · last Δ -5.1 (diff) · 24 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 · 24 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 0 Medium 12 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 24 Crowd 0 Layer: Software 1 Hardware 4 Security 6 Cicd 1 Quality 12

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 71.6/100 with 88.9% coverage. It contains 503 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 24 findings — concentrated in quality (12), security (6), hardware (4). Risk profile is high: 2 critical, 0 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 19 of 24 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in scripts/installer.py

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

scripts/installer.py:90

critical System graph security Secrets conf 1.00 Possible secret in src/telemetry.ts

Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.

src/telemetry.ts:162

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/matrix/gateway-transport.ts:188

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/matrix/media.ts:47

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/openclaw/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/relay/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/update/apply.ts:20

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

src/update/apply.ts:20 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/update/preflight.ts:19

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

src/update/preflight.ts:19 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/wizard.ts:33

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

src/wizard.ts:33 Node child process

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/installer.py:506

`subprocess.Popen(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/publish_npm.py:143

`subprocess.run(...)` 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 security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

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 Debug conf 1.00 Debug logging residue appears in source files

Found 39 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

docker/openclaw/Dockerfile:1 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1.91-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

docker/relay/Dockerfile:1 containersPinned dependencies

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `write_local_dsn_copy` in scripts/publish_npm.py:51

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 software Dead code conf 1.00 Possibly dead Python function: verify_plugin_registered

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/installer.py:596

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/bd92e337-e1cb-43b1-826f-2505c3fc118d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bd92e337-e1cb-43b1-826f-2505c3fc118d/

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.