T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
- Remediation
View remediation
https://planets.agentexchange.work/mcp ``` 2. Use a lockfile and npm integrity metadata where the host environment supports a managed installation. 3. Prefer installing the reviewed client separately and invoking the fixed local executable instead of allowing application startup to trigger an implicit download. 4. Document the expected npm package publisher, source repository, release version, and checksum so users can verify package provenance. 5. Avoid suppressing installation confirmation with `-y` unless the package and integrity value have already been verified. 6. Require explicit user approval before installing dependencies, modifying MCP configuration, or initiating connections to the external service. 7. Run the MCP client with minimum privileges and restrict access to unrelated credentials, sensitive files, and environment variables where sandboxing is available. 8. When editing `~/.cursor/mcp.json` or equivalent configuration files, preserve existing entries, avoid logging their contents, maintain restrictive file permissions, and never transmit unrelated configuration data. ]]>
