回退安装路径会直接执行未固定版本的 clerk@latest
原文依据:2 处当全局 CLI 不可用或不受信任时,Skill 建议通过 bunx、npx、pnpm dlx 或 yarn dlx 获取并执行 latest。latest 会随发布变化,审计过的 Skill 文档无法保证运行时下载的包仍是同一代码。
若包供应链、发布账号或最新版本受损,下载的代码会以代理的本机权限运行,并可能接触 Clerk 凭据、项目文件和网络。
当全局二进制不可用或版本不合适时,Skill 指示包运行器下载并执行 `clerk@latest`。该版本未固定,会随未来发布变化,因此当前文档审计不能覆盖实际运行的包。网络安装本身并非恶意,但用户可要求固定已审查版本、校验来源,或仅使用受管的全局安装。
> This skill targets clerk `latest`. If `clerk --version` disagrees with the latest available CLI, refresh it with `clerk update`, or invoke the latest through a package runner such as `bunx clerk@latest`. The binary is always the source of truth, so run `clerk <command> --help` to verify anything this skill claims.查看另外 1 个位置
Otherwise fall back to a package runner, in this order (matches the CLI's own `preferredRunner` logic, which prefers the runner that matches the project's lockfile):| Project package manager | Invocation || ------------------------- | -------------------------------- || bun (`bun.lock*`) | `bunx clerk@latest` || npm (`package-lock.json`) | `npx -y clerk@latest` || pnpm (`pnpm-lock.yaml`) | `pnpm dlx clerk@latest` || yarn >= 2 (`yarn.lock`) | `yarn dlx clerk@latest` |Yarn Classic (v1) has no `dlx`; treat those projects as "no preferred runner" and fall back to the first runner from the list above that's on PATH.