T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned Third-Party Package Installed Globally
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify the expected npm tarball integrity hash or signed provenance before installation. 3. Remove the recommendation to install `@latest` as a troubleshooting step. 4. Prefer a project-local dependency with a lockfile over a global installation. 5. Audit all direct and transitive dependencies, lifecycle scripts, and published package contents. 6. Where compatible with the package, install with lifecycle scripts disabled: ```bash npm install --ignore-scripts ``` 7. Run the daemon under a dedicated, minimally privileged operating-system account that cannot access unrelated user data. 8. Document the expected package publisher, source repository, version, checksums, and verification procedure so users can detect package substitution. ]]>
