T08 · Insecure Dependencies
- Location
SKILL.md:272- Finding
Unpinned Third-Party MCP Repository and Dependency Installation
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish the expected commit ID and release checksum in the Skill documentation so users can verify downloaded content before installation. 3. Replace floating Python requirements with exact versions and cryptographic hashes. Install them using hash verification: ```bash python -m pip install --require-hashes -r requirements.lock ``` 4. Review and lock all transitive dependencies rather than pinning only direct dependencies. 5. Install the MCP server in a dedicated virtual environment or isolated container under a low-privilege account. 6. Restrict the MCP process to the minimum required filesystem and network permissions. It should not receive unrelated OpenClaw credentials or workspace access. 7. Recommend reviewing repository changes, dependency provenance, and package installation hooks before updating to a newer commit or release. 8. Avoid claiming that the integration is configured or trusted solely because a token exists; document how credentials should be scoped, stored, and rotated. ]]>
