T08 · Insecure Dependencies
- Location
rules/install.md:5- Finding
Unpinned Third-Party CLI Installation with Privileged Fallback
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify package integrity information, such as the expected npm tarball integrity hash. 3. Remove the recommendation to run npm installation with `sudo`. 4. Recommend a user-scoped installation method, a version manager, or an isolated execution environment instead of a root-owned global installation. 5. Audit and document package lifecycle scripts before recommending the dependency. 6. Include the CLI source, a dependency lockfile, and reproducible build information in the reviewed project where practical. 7. Document the expected package publisher and official registry location to reduce dependency-confusion and package-spoofing risks. ]]>
