T08 · Insecure Dependencies
- Location
SKILL.md:45- Finding
Automatic Global Installation of an Unpinned Third-Party Package
- Content
View full analysis
- Remediation
View remediation
``` 3. Verify the package against an expected integrity digest or trusted signed provenance before use. 4. Disable lifecycle scripts with `--ignore-scripts` unless an audited installation script is strictly required. 5. Prefer a project-local, locked dependency over global installation. Commit an appropriate lockfile and verify it in deployment. 6. Run the CLI in a sandbox or least-privileged service account with access only to the required inventory database. 7. Include the CLI source or a verifiable dependency manifest in the audited artifact so the executable implementation can be reviewed. 8. Restrict registry configuration to a trusted registry and protect against dependency confusion or package-name substitution. ]]>
