An unpinned remote npm package executes locally with access to the API key
Source references: 4Every workflow uses `pnpm dlx @pilio/cli` without pinning a package version or verifying its contents. `pnpm dlx` can download and execute whichever package the registry serves at that time, in an environment containing `PILIO_API_KEY`. The evidence does not show malicious code, but updates, account compromise, or dependency compromise would directly affect users.
The package runs with the current user's permissions and could read accessible files and environment variables, modify the workspace, or transmit data, including the Pilio key.
The workflow requires PILIO_API_KEY and downloads/executes an unversioned `@pilio/cli` through `pnpm dlx`. The CLI can normally read inherited environment variables, so a later-compromised package, maintainer account, or dependency could expose the key or abuse local permissions. The evidence does not show that the package is malicious. Users can ask for a pinned, verified version or run it in isolation with a restricted, revocable key.
Require `PILIO_API_KEY` in the environment. Do not ask the user to paste API keys into the conversation.Show 3 other places
```bashpnpm dlx @pilio/cli gpt-image-2 --prompt "<prompt>" --aspect-ratio "1:1"``````bashpnpm dlx @pilio/cli gpt-image-2 --input ./reference.png --prompt "<edit prompt>"``````bashpnpm dlx @pilio/cli task wait <task_id>```