T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned Third-Party Package Installation and Immediate Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify a cryptographic integrity hash or signed release artifact before installation. Document the expected npm registry and package publisher identity. 3. Avoid `npx -y` because it automatically approves retrieval and execution. Require explicit operator confirmation and display the exact version being executed. 4. Review whether the package requires npm lifecycle scripts. If it does not, install with `--ignore-scripts`. If lifecycle scripts are required, audit and document them before recommending execution. 5. Prefer a lockfile-backed local installation or a verified standalone binary whose version, checksum, and signature are pinned in the Skill documentation. 6. Link to auditable source code corresponding exactly to the pinned release and document a reproducible method for confirming that the distributed package matches that source. 7. Run the CLI as an unprivileged user and expose only the files, output directories, and credentials required for the requested RunComfy operation. Never recommend installation with `sudo`. 8. Treat the package as an external executable trust boundary. Independently verify its claimed network endpoint allowlist, token handling, telemetry behavior, and output-download restrictions before relying on those claims. ]]>
