T08 · Insecure Dependencies
- Location
references/pre-commit-config.yaml:4- Finding
Pre-commit Hooks and Additional Dependencies Are Not Immutably Pinned
- Content
View full analysis
- Remediation
View remediation
``` 3. Where the package installation mechanism supports it, require verified package hashes and use a controlled dependency lock file or constraints file. 4. Configure package installation to use a trusted, controlled package index rather than arbitrary or unintended indexes. 5. Review automated dependency updates before merging them. Ensure updates modify pinned SHAs or exact package versions through auditable pull requests. 6. Run pre-commit hooks in an isolated CI environment with least-privilege credentials, restricted filesystem access, and limited outbound network access. 7. Avoid exposing production secrets or broadly scoped repository tokens to jobs that install and execute third-party hooks. 8. Periodically verify pinned commits against upstream release provenance and security advisories. ]]>
