SafeHub

Scan OpenClaw skills for malware and security issues before installation. Use when the user wants to verify a skill is safe, audit a ClawHub skill, or check...

SafeHub's implementation is coherent with its stated purpose, but pay attention to these practical risks before installing or running it: (1) The 'update' command will fetch and overwrite the scanner's rule files from whatever GitHub repo you point it at — only use a rules repo you trust, and avoid running update against unknown forks. (2) The Docker sandbox runs the target read-only with no network, but the code does not actually instrument or report detailed runtime behavior (networkAttempted and sensitiveReads are not detected), so do not rely solely on the sandbox to prove safety. (3) Cached reports are stored in ~/.safehub and a Docker named volume may be created; review/delete these if they contain sensitive metadata. (4) Because the tool executes git clone on GitHub URLs and starts containers via the Docker daemon, run SafeHub in an isolated environment (or inspect the code locally) if you are scanning untrusted repos. If you plan to rely on SafeHub's results, review scanner/static.js and scanner/scorer.js to understand exactly what patterns are detected and how the trust score is computed.

Type: OpenClaw Skill Name: safehub Version: 1.0.2 SafeHub is a security scanner that contains a critical shell injection vulnerability in lib/resolve.js, where a GitHub URL is passed directly into execSync for a git clone operation without sufficient sanitization. Additionally, the update command in commands/update.js allows the tool to fetch and overwrite local rule files from an arbitrary GitHub repository (controlled by the SAFEHUB_RULES_REPO environment variable), which could be leveraged to manipulate scan results or potentially exploit the host. While the tool implements a restrictive Docker sandbox for dynamic analysis, these architectural flaws and the remote-update mechanism pose a significant security risk.