T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local installation over `npm install -g` and invoke the binary from the local dependency directory. Run it in a sandbox or container with access limited to the files and network destinations required for bookmark retrieval. 3. Commit a lockfile produced from the reviewed dependency graph and use a reproducible installation command such as: ```bash npm ci --ignore-scripts ``` Only permit lifecycle scripts after reviewing why they are required. 4. Document the expected package publisher, source repository, exact version, and package integrity hash. Verify these values before installation and after version updates. 5. Audit direct and transitive dependencies before upgrading. Use automated dependency monitoring, but require manual security review before accepting new package versions. 6. Limit runtime access to the X authentication directory and bookmark archive. Do not expose unrelated workspace files or unnecessary environment variables to the CLI. 7. Keep optional webhook credentials out of the CLI process environment when they are not required. Require explicit user confirmation before the first external delivery of private bookmark summaries. 8. Document an uninstall and credential-revocation procedure for users who suspect dependency compromise. ]]>
