So what are you (the ESLint team) going to do to ensure this is not going to happen again in the future?
At the very least you should require that all ESLint members with rights to publish ESLint packages have 2FA enabled on their npm account.
At the very least you should require that all ESLint members with rights to publish ESLint packages have 2FA enabled on their npm account.
No comments yet.