T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Global npm Dependency Creates Supply-Chain Execution Risk
- Content
View full analysis
- Remediation
View remediation
`, rather than resolving the mutable latest release. - Record and verify package integrity where the deployment mechanism supports it. - Prefer a project-local installation over a global installation unless global availability is strictly necessary. - Require explicit user confirmation before performing the global installation, while avoiding redundant confirmation if the user already approved the exact operation in the current turn. - Review the pinned package's lifecycle scripts and transitive dependency tree before approving it. - Avoid running npm installation with administrative privileges. - Establish an update process that reviews and tests new versions before changing the pin. ]]>
