T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party Dependency Creates a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
``` 2. Store dependencies in a requirements or lock file with cryptographic hashes and install them using hash enforcement: ```bash python -m pip install --require-hashes -r requirements.txt ``` 3. Generate and review hashes from a trusted package source before deployment. 4. Configure `pip` to use an explicitly trusted package index and prevent unintended fallback to untrusted or privately controlled indexes. 5. Run dependency installation and the Skill under a dedicated, least-privileged account or isolated virtual environment. 6. Review package source code and release provenance before changing the pinned version. 7. Use dependency and software-composition scanning in the release process, and update the pin only after testing and security review. 8. Keep the metadata dependency declaration consistent with the reviewed lock file so automated installers cannot silently select a different release. ]]>
