GitHub will soon require all developers who contribute code on the platform to enable two-factor authentication (2FA) for improved security. And it will begin rolling out this requirement on Monday, March 13.

“GitHub is central to the software supply chain, and securing the software supply chain starts with the developer,” a new post to the GitHub blog explains. “Our 2FA initiative is part of a platform-wide effort to secure software development by improving account security. Developers’ accounts are frequent targets for social engineering and account takeover (ATO). Protecting developers and consumers of the open source ecosystem from these types of attacks is the first and most critical step toward securing the supply chain.”

Last May, GitHub announced that it would require all contributors to enroll in 2FA by the end of 2023. This week’s announcement concerns the beginning of that rollout: starting Monday, GitHub will begin contacting smaller developer groups about the 2FA requirement, and it will then scale the requirement to larger groups as the year progresses.

When your account is selected for enrollment in 2FA, you will see notifications on the GitHub and website and via email. From that point, you will have 45 days to configure 2FA on your account, and you will receive notifications when the enablement deadline is getting close. If you let the deadline pass, GitHub will require you to enable 2FA the next time you access the GitHub website, and you can snooze it for up to a week. But after that, your account access will be limited.

Or, you could just do the smart thing—the right thing—and enable 2FA now. You can do so at any time, as explained on the GitHub website.