T08 · Insecure Dependencies
- Location
SKILL.md:63- Finding
Unpinned Third-Party CLI Installation and Execution
- Content
View full analysis
- Remediation
View remediation
npx --yes @runcomfy/cli@ ``` 2. Document the expected package version, official npm registry, publisher identity, and package integrity hash so users can verify what will execute. 3. Prefer a committed lockfile and `npm ci` for managed deployments rather than dynamically resolving the latest release. 4. Disable npm lifecycle scripts where compatible with the package: ```bash npm install --global --ignore-scripts @runcomfy/cli@ ``` Confirm first that the legitimate CLI does not require installation scripts. 5. Recommend executing the CLI under a non-privileged account or within a restricted container. Grant access only to the intended output directory and the RunComfy credential required for the request. 6. Avoid exposing unrelated secrets to the CLI process. Supply only `RUNCOMFY_TOKEN`, and use a narrowly scoped or short-lived token if RunComfy supports one. 7. Establish an update-review process: verify new CLI releases and their dependency changes before updating the pinned version. ]]>
