安装并认证第三方 npm CLI 会让其代码以用户权限运行并接触账户令牌
原文依据:4 处说明要求通过全局 npm 安装或 `npx -y` 自动下载并执行 `@runcomfy/cli`,随后使用该程序登录。提供的材料不包含 CLI 实现,因此无法核验其安装脚本、文件访问范围或令牌处理是否符合这里的声明。
如果软件包、发布账户或依赖项被入侵,执行的代码可能读取当前用户可访问的文件或环境变量,并可能盗用 RunComfy 令牌和账户额度。
说明明确要求下载并执行第三方 npm CLI,然后用其登录或向其提供环境变量令牌。这是实现音乐服务所需且已披露的操作,但 CLI 源码未在材料中,无法独立核验其安装脚本、文件访问或令牌保护声明。用户可在隔离环境运行、固定版本,并限制令牌权限与余额。
**Step 1 — install** (one of, see the `runcomfy-cli` skill for details):```bashnpm i -g @runcomfy/cli # global installnpx -y @runcomfy/cli --version # zero-install```**Step 2 — sign in** (or set `RUNCOMFY_TOKEN` env var in CI / containers):```bashruncomfy login```查看另外 3 个位置
- **Install via verified package manager only.** Use `npm i -g @runcomfy/cli` or `npx -y @runcomfy/cli`. **Agents must not pipe an arbitrary remote install script into a shell on the user's behalf** — if the operator wants the curl-pipe path documented at `docs.runcomfy.com/cli/install`, they should review the script first.- **Token storage**: `runcomfy login` writes the API token to `~/.config/runcomfy/token.json` with mode 0600. Set `RUNCOMFY_TOKEN` env var to bypass the file in CI / containers. Never echo the token into a prompt, log it, or check it in.- **Input boundary (shell injection)**: prompts and audio URLs are passed as a JSON string via `--input`. The CLI does not shell-expand prompt content; it transmits the JSON body directly to the Model API over HTTPS. **No shell-injection surface from prompt content**.```bashnpm i -g @runcomfy/cli # global installnpx -y @runcomfy/cli --version # zero-install```**Step 2 — sign in** (or set `RUNCOMFY_TOKEN` env var in CI / containers):```bashruncomfy login```