T08 · Insecure Dependencies
Warning
- Location
SKILL.md:30- Finding
Unpinned Third-Party Dependencies and Mutable Remote Model Artifacts
- Content
View full analysis
- Remediation
View remediation
soundfile== numpy== transformers== ``` 2. Generate and commit a lock file containing all transitive dependencies. Use integrity hashes, such as pip's `--require-hashes`, to prevent silent artifact substitution. 3. Install dependencies from a controlled package index or trusted internal mirror where feasible. 4. Record and verify the expected FFmpeg version. For reproducible deployment, use a controlled binary artifact with a published checksum rather than resolving an unconstrained current Homebrew formula. 5. Pin each remote model to an immutable repository commit or revision instead of relying only on its mutable repository name. 6. Publish and verify cryptographic checksums for all downloaded model files before loading them. 7. Cache approved model artifacts in a trusted, access-controlled location and configure the application to operate offline after provisioning. 8. Document that the first execution performs network retrieval and identify the exact package registries and model hosts contacted. 9. Run installation and inference under a dedicated, non-privileged account with restricted filesystem and network access to reduce the impact of a compromised dependency. 10. Add automated dependency and artifact verification to continuous integration, including vulnerability scanning and alerts for unexpected lock-file or model-hash changes. ]]>