T08 · Insecure Dependencies
- Location
README.md:35- Finding
Unpinned Third-Party Package Installation and Automatic Execution
- Content
View full analysis
- Remediation
View remediation
" ``` 2. Publish cryptographic hashes for approved distributions and require hash verification: ```text gprophet== \ --hash=sha256: ``` 3. Supply a lockfile or requirements file generated from reviewed artifacts, and install with hash enforcement: ```bash pip install --require-hashes -r requirements.txt ``` 4. Pin the `uvx` source to an exact version rather than allowing it to resolve the latest package: ```json { "command": "uvx", "args": ["--from", "gprophet==", "gprophet-mcp"] } ``` 5. Identify the authoritative package registry page, source repository, publisher identity, and release-signing process in the documentation. 6. Include the MCP server source in the audited artifact, or link each package release to an immutable source commit so reviewers can verify the executed implementation. 7. Run the MCP server in an isolated environment with restricted filesystem and network access. Supply a limited-scope API key with conservative quotas rather than a broadly privileged production key. 8. Document a package-update review process that verifies source changes, package provenance, signatures, and artifact hashes before changing the pinned version. ]]>
