T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
- Remediation
View remediation
mcp ``` 2. Prefer installing through a project manifest and lockfile rather than resolving the package dynamically during every invocation. 3. Verify package integrity using the package manager's integrity metadata or a separately published cryptographic checksum. 4. Document the expected npm publisher, repository, version, and release checksum so users can verify provenance. 5. Remove automatic confirmation where practical and explain that the command downloads and executes third-party code. 6. Run the MCP server under a dedicated, minimally privileged operating-system account or container. 7. Restrict the Lark application to only the API scopes required for the intended deployment. 8. Review new package versions before updating the pinned version. ]]>
