T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Record and verify package integrity information through a lockfile, trusted checksum, package signature, or equivalent reproducible verification mechanism. 3. Prefer a project-local installation over a global installation so the dependency is isolated and its version is controlled: ```bash npm install --save-exact agent-browser@ npx agent-browser ``` 4. Review the selected package release, including its lifecycle scripts and transitive dependencies, before updating the pinned version. 5. Avoid recommending `@latest` in troubleshooting documentation. Provide a documented upgrade process that requires security review and compatibility testing. 6. Run installation without elevated privileges and in a sandboxed or otherwise restricted environment where practical. 7. Keep the root and nested copies synchronized so remediated installation guidance is applied consistently to both copies. ]]>
