T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
- Remediation
View remediation
``` 2. Require cryptographic hash verification. Maintain a requirements file containing exact versions and hashes, then install it with: ```bash python -m pip install --require-hashes -r requirements.txt ``` 3. Lock all transitive dependencies rather than pinning only the direct package. Regenerate the lock file through a controlled dependency-review process. 4. Verify that the PyPI package publisher and release artifacts correspond to the referenced source repository. Document explicitly that this is a third-party CLI rather than an official Google package unless official status can be independently established. 5. Install and execute the CLI in an isolated virtual environment or container using a non-privileged account. Do not recommend installation with `sudo` or into a privileged system Python environment. 6. Review new package releases before updating the pinned version. Include source review, dependency-diff review, malware scanning, and provenance or signature verification where available. 7. Minimize credential exposure by restricting filesystem permissions around authentication state and by avoiding environments containing unrelated secrets. 8. Apply the same hardened installation instructions consistently in both `SKILL.md` and `references/quick-ref.md`. ]]>
