T08 · Insecure Dependencies
- Location
SKILL.md:71- Finding
Unpinned Global Installation of a Privileged Third-Party CLI
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish the expected package version and integrity digest in the Skill documentation, and verify package provenance before installation. 3. Prefer a project-local dependency with a committed lockfile over a global installation. Invoke it through a controlled package script or an equivalent isolated mechanism. 4. Avoid running npm installation commands with `sudo`, as administrator, or from another privileged account. 5. Disable installation lifecycle scripts where operationally possible, or explicitly document and audit any lifecycle scripts the package requires. 6. Run the CLI under a dedicated least-privileged account or sandbox with access only to the required token, input references, and output directory. 7. Restrict outbound traffic to the documented RunComfy API and download domains, and verify that the installed CLI does not contact unexpected destinations. 8. Rotate the RunComfy token and investigate local file access if package compromise is suspected. ]]>
