T08 · Insecure Dependencies
- Location
SKILL.md:198- Finding
Unpinned Third-Party Dependencies and Mutable Installation Sources
- Content
View full analysis
- Remediation
View remediation
" ``` 3. Publish and verify cryptographic hashes, using pip hash-checking mode where practical: ```bash python3 -m pip install --require-hashes -r requirements.txt ``` 4. Pin repository-based installations to an immutable commit digest or signed release rather than a mutable branch or package identifier. 5. Provide a lockfile or fully resolved dependency manifest covering transitive dependencies. 6. Document the authoritative registry and publisher identity so users can detect dependency-confusion or namespace-spoofing attempts. 7. Remove automatic upgrade behavior from standard setup instructions. Review new releases before updating the pinned version. 8. Recommend installation inside an isolated virtual environment or container and explicitly discourage elevated installation. 9. Validate package signatures or release attestations when supported, and incorporate dependency scanning into the release process. ]]>
