T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party npm Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
link ``` 2. Avoid recommending global installation. Use a project-local development dependency with a committed lockfile: ```bash npm install --save-dev --save-exact shersh@ ``` 3. Commit and review `package-lock.json`, and use `npm ci` in controlled environments to enforce locked dependency resolution. 4. Verify package provenance, expected publisher identity, registry source, and integrity metadata before execution. 5. Review package lifecycle scripts and dependency changes when upgrading. Where operationally feasible, disable lifecycle scripts during installation and explicitly invoke only reviewed functionality. 6. Run the deployment tool in an isolated, least-privilege environment with restricted filesystem, credential, and network access. 7. Document the trusted package version and an upgrade-review process so future releases are not executed automatically without reassessment. ]]>
