T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
- Remediation
View remediation
``` 2. Distribute a hash-locked requirements file and require hash verification: ```bash pip install --require-hashes -r requirements.txt ``` 3. Record hashes for every package artifact and transitive dependency used by the installation. 4. Review the source and published artifact for the pinned release, including build-system configuration and installation hooks. 5. Use a trusted package index and explicitly configure the expected index to reduce dependency-confusion and repository substitution risks. 6. Install and execute the package in an isolated virtual environment or container under a dedicated, least-privileged account. 7. Restrict filesystem, credential, environment-variable, and network access for the MCP server and maintenance processes to only what memory management requires. 8. Adopt a controlled update process in which dependency upgrades are reviewed, tested, scanned, and assigned new integrity hashes before deployment. 9. Update both the metadata declaration and installation example so automated installers and human operators use the same pinned, verified release. ]]>
