GitHub Hardens npm and Actions Defaults to Disrupt Supply Chain Attacks

GitHub has consolidated the security changes it shipped across npm and GitHub Actions between March and July 2026, a batch of default-on controls designed to disrupt software supply chain attacks, InfoQ reported on August 8. Principal product security engineer Greg Ose and principal software engineer Zachary Steindler frame the problem as one without a single fix — these attacks chain several weaknesses together, so GitHub prioritized the mitigations that break the most impactful links.

Hardening the Entry Points

npm now places high-impact accounts into read-only mode for 72 hours when they change their email address or use a 2FA recovery code. On the Actions side, the default behavior of actions/checkout changed so workflows no longer check out untrusted fork code under commonly exploited triggers unless a team explicitly opts out — a change that was backported, so it also reaches pipelines pinned to earlier releases.

Closing Escalation and Exfiltration Paths

Workflow execution policies let administrators govern who may trigger workflows and which trigger types are permitted, while the Actions cache is now read-only for untrusted triggers, closing the path where an attacker poisons a shared cache entry to reach privileged release workflows. On credentials, GitHub's guidance is blunt: removing long-lived credentials from the pipeline is the single most effective step, and npm trusted publishing now supports CircleCI. An Actions network firewall is in technical preview, logging outbound traffic so teams can spot unusual destinations.

Slowing Propagation

npm staged publishing holds versions until an additional approval and 2FA step completes, and npm v12 disables install scripts by default along with dependencies fetched via git or remote URLs. Dependabot version updates now wait three days before opening a pull request. The debate continues: practitioners note the industry keeps building process gates while declining author-side package signing of the kind Linux distributions have had since the 1990s — npm has rejected pull requests implementing it, even optionally, for a decade. The strongest protections, staged and trusted publishing, remain opt-in.