Openclaw Installer Cn
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user asking for a repair could have packages, permissions, and configuration changed before reviewing the exact commands.
The skill tells the agent that a quick-fix request should automatically perform mutating repair actions, but it does not define approval gates or precise limits for those actions.
### 快速修复 ``` 修复 OpenClaw 安装问题 ``` 自动执行： - 清理缓存 - 重装依赖 - 修复权限 - 更新配置
Make diagnosis the default, show the exact commands and target paths, and require explicit user approval for each mutating repair step.
This could weaken or break system package ownership and affect other Node/npm tools on the machine.
These commands require elevated privileges and recursively change ownership of npm and global Node module paths, including a protected system-wide location.
sudo chown -R $(whoami) ~/.npm sudo chown -R $(whoami) /usr/local/lib/node_modules
Prefer a user-local npm prefix or nvm; if a permission fix is still needed, ask for explicit approval and scope it to the minimum verified OpenClaw-related path.
If the remote source or delivery path is compromised, arbitrary commands could run on the user's machine.
The skill recommends piping a downloaded remote script directly into a shell, with no checksum, signature verification, or inspection step.
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
Download and inspect installer scripts first, verify integrity from official documentation, and require user confirmation before execution.
If run in the wrong project, this could remove a lockfile, change dependency resolution, and break or alter unrelated work.
The cleanup commands delete dependency artifacts in the current directory without specifying that the directory has been verified as an OpenClaw install path.
npm cache clean --force rm -rf node_modules rm package-lock.json # 重装 npm install
Validate the target directory, back up lockfiles, and ask the user before any rm or reinstall command.
The user may install whatever package version is served by the mirror at that time.
Global package installation from an external mirror is relevant to the installer purpose, but the package versions and provenance checks are not specified.
npm install -g cnpm --registry=https://registry.npmmirror.com cnpm install -g openclaw
Use official sources where possible, pin known-good versions, and verify package provenance before global installation.
API keys placed in shell profiles can be exposed if dotfiles are shared, backed up insecurely, or copied into support requests.
The skill proposes storing provider API keys as persistent shell-profile environment variables; this is expected for model-provider setup, but it is not declared in the registry metadata.
export DEEPSEEK_API_KEY="your-key-here" export ZHIPU_API_KEY="your-key-here"
Enter real API keys manually, avoid sharing shell profiles, and consider a secrets manager or restricted-permission env file.