T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned Third-Party CLI Installation from Mutable Sources
- Content
View full analysis
- Remediation
View remediation
' --locked ``` 2. For source installation, check out an immutable audited commit rather than the mutable default branch: ```bash git clone https://github.com/vincentzhangz/singleshot cd singleshot git checkout --detach '' cargo install --path . --locked ``` 3. Publish expected SHA-256 checksums or cryptographic signatures for release artifacts and require users to verify them before installation. 4. Prefer a trusted and reproducible distribution channel. If the third-party Homebrew tap remains supported, pin an audited formula revision and document how users can verify the formula and downloaded artifact. 5. Add release provenance controls, such as signed Git tags, signed release artifacts, protected publisher accounts with multi-factor authentication, and build attestations. 6. Document the expected package publisher, repository, exact version, commit identifier, and integrity values so users can detect dependency confusion or publisher substitution. 7. Run the CLI with least privilege and expose only the provider credential needed for the current command. Avoid installing or executing it from an administrator account. 8. Review and update pinned versions deliberately, repeating the security review and integrity verification before changing the documented version or commit. ]]>
