Installation executes an unpinned npm package and may install it globally
Source references: 2The documentation recommends either globally installing @runcomfy/cli or using npx -y to automatically download and execute the currently resolved version. No exact version or package-integrity value is pinned.
If the npm account, publication chain, or a newly resolved release is compromised, install scripts or the CLI could execute code with the user's permissions. A global install also persistently changes the machine's tool environment.
The documentation offers an unpinned global npm installation and an `npx -y` download-and-run alternative. Execution uses whichever package version npm resolves at that time; the global form also changes the system-wide Node tool environment. The package-manager warning does not supply a version pin or package digest.
```bash# 1. Install (see runcomfy-cli skill for details)npm i -g @runcomfy/cli # or: npx -y @runcomfy/cli --version# 2. Sign inruncomfy login # or in CI: export RUNCOMFY_TOKEN=<token>Show 1 other places
- **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**.- **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.