T08 · Insecure Dependencies
- Location
SKILL.md:62- Finding
Unpinned Third-Party Repository and SDK Dependencies
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify signed release tags or signed provenance before installation. 3. Pin every direct and transitive Python dependency to an exact reviewed version. 4. Generate a hash-locked requirements file and require hash verification: ```bash pip install --require-hashes -r requirements.lock ``` 5. Pin the SDKs to exact reviewed versions rather than resolving the latest available releases: ```bash pip install reversal-sdk== npm install --save-exact reversal-client@ ``` 6. Commit and enforce an npm lockfile with integrity metadata, and use `npm ci` for reproducible installation. 7. Audit package ownership, release provenance, dependency names, and lifecycle scripts before recommending the packages. 8. Run installation and the MCP server in a dedicated, non-administrative, isolated environment with minimal filesystem access and without unrelated credentials. 9. Add automated dependency scanning and establish a controlled process for reviewing and updating pinned versions. ]]>
