T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Third-Party CLI Dependency Installation
- Content
View full analysis
- Remediation
View remediation
" ``` 2. Keep the version constraint consistent across the `uv-tool`, `pipx`, and `pip` installation metadata. 3. Verify package integrity using registry-supported hashes, signatures, attestations, or a locked dependency manifest where available. 4. Document the expected package registry and upstream repository so package resolution cannot silently use an unintended mirror or index. 5. Review new package versions before updating the pin. Include dependency and provenance checks in the release process. 6. Recommend installing and running the CLI in a least-privileged, isolated environment without unrelated credentials or sensitive files. 7. Avoid advising users to force-upgrade directly to an unreviewed latest release. Replace the documented `--force` upgrade guidance with installation of a specifically approved version. ]]>
