DECODING THE GITHUB RECOMMENDATIONS FOR NPM MAINTAINERS

Summary from the TLDR InfoSec newsletter

Following recent npm supply chain attacks, GitHub's hardening guidance centers on three controls: adopting Trusted Publishing Framework (OIDC-based short-lived credentials instead of long-lived tokens), enforcing 2FA for all publishing operations, and using WebAuthn/passkeys instead of TOTP for phishing-resistant authentication. npm deprecated new TOTP setups in October and disabled legacy tokens in November, requiring maintainers to use granular access tokens with expiration for CI/CD automation. Maintainers should configure trusted publisher relationships in package settings, enable 2FA across all sensitive operations, and enroll WebAuthn authenticators while maintaining repository access controls.