T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Installed Globally
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify the expected package integrity hash or npm provenance before installation. 3. Link to the package's canonical registry and source repository so users can verify its identity and avoid similarly named packages. 4. Prefer a project-local installation with a committed lockfile over a global installation where operationally possible. 5. Use `npm ci` in automated environments to enforce lockfile-resolved versions and integrity metadata. 6. Review package lifecycle scripts before installation. Where compatible with the package, install with lifecycle scripts disabled: ```bash npm install --ignore-scripts ``` 7. Periodically review and explicitly approve upgrades rather than implicitly installing the latest registry release. ]]>
