T08 · Insecure Dependencies
- Location
SKILL.md:369- Finding
Unpinned Package Execution and Automatic Dependency Modification
- Content
View full analysis
- Remediation
View remediation
-u ``` 2. Prefer installing the reviewed tool as a development dependency and invoking the lockfile-resolved binary: ```bash npm install --save-dev --save-exact npm-check-updates@ npm exec npm-check-updates -- -u ``` 3. Use a trusted registry and enforce registry configuration to reduce dependency-confusion and source-substitution risks. 4. Commit and validate a lockfile. Review package provenance, integrity metadata, maintainership, and dependency changes before installation. 5. Run `npm audit` in reporting mode first. Avoid applying `npm audit fix` automatically in sensitive projects; inspect the proposed dependency diff and apply tested upgrades deliberately. 6. Review all manifest and lockfile changes generated by dependency tools. Run automated tests and security scans before merging or deploying them. 7. Where practical, disable package lifecycle scripts during initial inspection: ```bash npm install --ignore-scripts ``` Enable required scripts only after reviewing the affected packages. 8. Execute dependency-maintenance commands in an isolated, least-privileged environment without production credentials or unrelated filesystem access. ]]>
