Block risky GitHub Actions triggers

Updated: 2026.11.22 4H ago 1 sources
A short operational precedent: the Python Software Foundation audited and disabled specific GitHub Actions triggers (e.g., pull_request_target, issue_comment) across its organizations and published rollout documentation so other projects can apply the same org‑level policies. The writeup links repeated supply‑chain 'pwn request' incidents to apparently innocent workflow lines and shows how platform policy (Team/Enterprise org policy or per‑repository settings on Free plans) can stop them centrally. — This shows a practical lever — platform org policies — that open‑source projects and platform regulators can use to reduce a recurring CI‑based supply‑chain risk across many repositories at scale.

Sources

Python Devs Document 'De-fanging Dangerous Triggers In GitHub Actions'
EditorDavid 2026.11.22 100% relevant
Python Software Foundation security developers Seth Larson and Mike Fiedler documented the problem (pwn requests via pull_request_target/issue_comment), applied blocking policies to psf/python/pypi GitHub organizations, and published technical rollout guidance.
← Back to all ideas