T08 · Insecure Dependencies
- Location
SKILL.md:50- Finding
Unpinned Remote npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
- Remediation
View remediation
`. 2. Manage the package through a controlled project dependency workflow with a committed lockfile rather than downloading it dynamically on every launch. 3. Verify package integrity using an approved registry, lockfile integrity metadata, and organizational dependency controls. 4. Review the selected package version and its transitive dependencies before deployment. 5. Avoid automatic confirmation through `npx -y` where operationally feasible, particularly for packages that have not already been installed and verified. 6. Run the MCP server with least privilege and restrict access to sensitive files, credentials, environment variables, and network destinations. 7. Use automated dependency monitoring and require explicit review before upgrading the pinned version. ]]>
