GitHub Hardens npm and Actions Defaults, Drawing Debate over Delays versus Signing

GitHub has implemented a series of security hardening measures across npm and GitHub Actions from March to July 2026, aiming to mitigate supply chain attacks which often involve a chain of weaknesses. Greg Ose, principal product security engineer, and Zachary Steindler, principal software engineer, noted that there is no single solution to these attacks and have focused on mitigations that disrupt the most impactful links.

For npm, high-impact accounts will be set to read-only for 72 hours following changes to their email address or 2FA recovery code. Additionally, when workflows check out untrusted fork code under commonly exploited triggers, GitHub Actions will no longer do so as the default behavior of actions/checkout. To prevent escalation, workflow execution policies allow administrators to govern who can trigger workflows and which trigger types are permitted.

The Actions cache has also been set to read-only for untrusted triggers, closing a potential path for an attacker to poison shared cache entries to reach privileged release workflows.

Regarding credential exfiltration, it is recommended to remove long-lived credentials from the pipeline and use npm trusted publishing that supports CircleCI. GitHub Actions network firewall is in technical preview, logging outbound traffic for unusual destinations. npm v12 will disable install scripts by default and disable dependencies fetched via git or remote URLs by default. Dependabot version updates will wait for three days before opening a pull request.

Community reactions on Hacker News have been divided, with some arguing that time delays are an ineffective solution to the problem, while others claim that author-side package signing is the most effective mitigation, which GitHub has declined to implement for a decade due to potential deterrence of contributors.