T08 · Insecure Dependencies
Warning
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Installation Followed by Setup Execution
- Content
View full analysis
- Remediation
View remediation
" ``` 2. Require installation from a lock file or artifact with a verified SHA-256 hash. 3. Use `--require-hashes` where practical and document the expected package index explicitly. 4. Separate package installation from `flue setup` so the resolved package and setup behavior can be inspected before execution. 5. Display the package name, exact version, source, integrity hash, and expected setup changes when requesting approval. 6. Prefer a dedicated virtual environment and run setup with the least-privileged user account needed for application automation. 7. Review package metadata, dependencies, setup behavior, and adapter scripts before endorsing a release. 8. Do not use elevated privileges unless a separately documented and narrowly scoped operation genuinely requires them. ]]>
