T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local installation and invoke it through a package script or `npx --no-install` rather than modifying the global tool environment. 3. Commit and verify an npm lockfile so dependency resolution remains reproducible. 4. Verify package provenance, publisher identity, registry source, and integrity metadata before installation. 5. Disable lifecycle scripts during installation where compatible: ```bash npm install --ignore-scripts ``` 6. Review any required lifecycle scripts separately before allowing them to run. 7. Run the CLI under a least-privileged account or sandbox with restricted filesystem and network access. 8. Document the approved package source and update process, including security review requirements before changing the pinned version. ]]>
