Astral, the maintainer of widely‑used tools such as Ruff, uv and ty, published a detailed account of its supply‑chain hardening after recent breaches like the Trivy and LiteLLM incidents. The company argues that developers expect the build, test and release pipelines to be trustworthy, so it is laying out the safeguards that protect its own code and those who depend on it.

To keep CI/CD secure, Astral runs all workflows on GitHub Actions but disables high‑risk triggers such as pull_request_target and workflow_run across the organization. Every action must be pinned to a full‑length commit SHA, a practice reinforced by zizmor’s audits and GitHub’s own policy, achieving full hash‑pinning of the dependency graph. Manual reviews catch any remaining mutable references, and tools like pinact automate the pinning process.

Beyond pipelines, Astral limits privileged accounts, requiring strong TOTP‑based 2FA for every member and restricting admin roles to a handful of users. Organization‑wide branch protection forbids force‑pushes to main, while tag rules make releases immutable until a manual approval step passes. By enforcing these controls at the org level, even a compromised repository admin cannot bypass the safeguards.