T08 · Insecure Dependencies
- Location
references/install.md:14- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
- Remediation
View remediation
" ``` 2. Publish the expected package version, official repository, package index, artifact filename, and SHA-256 checksum in the installation documentation. 3. Prefer installation from a locked dependency manifest containing cryptographic hashes. Where standard `pip` is used, enforce hash verification: ```bash python3 -m pip install --require-hashes -r requirements.lock ``` 4. Explicitly select the trusted package index and disable unexpected fallback indexes where operationally appropriate: ```bash python3 -m pip install \ --index-url https://pypi.org/simple \ --no-deps \ --require-hashes \ -r requirements.lock ``` 5. Audit the pinned `deepxiv-sdk` artifact and its transitive dependencies before documenting it as approved. Repeat the audit before updating the pin. 6. Prefer prebuilt, verified wheels and reject unexpected source distributions where feasible, reducing exposure to package build-time code. 7. Retain the existing requirement for explicit user approval and show the exact version, source, and checksum to the user before installation. 8. Keep installation isolated through `pipx` or a dedicated virtual environment, run it without administrative privileges, and avoid placing secrets in the installation or runtime environment. ]]>
