T08 · Insecure Dependencies
- Location
guides/01-installation.md:113- Finding
Unpinned Third-Party Package Execution and Persistent MCP Registration
- Content
View full analysis
- Remediation
View remediation
" ``` 4. Use a requirements file with cryptographic hashes and install with: ```bash pip install --require-hashes -r requirements.txt ``` 5. If npm is genuinely required, pin an exact reviewed version, retain lockfile integrity metadata, and avoid automatic confirmation: ```bash npx --package "scrapling-mcp@" scrapling-mcp ``` 6. Prefer project-scoped MCP registration over `--scope user` so the server is not automatically exposed to unrelated future projects. 7. Pin Docker images by immutable digest instead of using `latest`: ```bash docker pull d4vinci/scrapling@sha256: ``` 8. Document the expected publishers, package registry URLs, versions, checksums, and verification procedure. 9. Run browser tooling and MCP servers in a restricted environment with minimal filesystem access, sanitized environment variables, and limited outbound network access. 10. Require explicit user approval before downloading executable dependencies or modifying persistent MCP configuration. ]]>
