-
Notifications
You must be signed in to change notification settings - Fork 1k
Email all owners when a new version of a package is uploaded #997
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This should be an opt-in per-maintainer/owner. The volume of email traffic that warehouse would generate would be rather enormous otherwise. |
I think I agree that this needs to be opt-in per maintainer/owner. It might also make sense to do something GitHub-esque here and have on page notifications and email notifications and let people configure how they want to receive which kind of information (though that's not strictly related to this ticket). |
Thanks for the suggestion and the discussion. We talked about this feature today and, since it's a new feature that isn't on Legacy PyPI, we've moved it to a future milestone. |
To do this the right way, we should wait till we have #5863 implemented, so we can draw on the event logging and use it to trigger this notification. |
Now unblocked! Should we do this through #5714? |
Forward duping to #13234. |
To make account compromise more obvious, it would be great if package owners (and maybe also maintainers) were emailed when a new version of a package was uploaded, thereby alerting them if this was unexpected.
Now an attacker could of course change the email address associated with an owner account, however doing this should result in an "email changed" notification (will file a separate issue), which will alert the owner anyway.
It may be that these notifications will need an opt-out, in which case we'll need to protect against an attacker turning them off (this could be achieved by 2FA, or by sending a "notifications settings changed" email). Though in the case of multiple owners of a package, even if an attacker turned them off for one account, the others would still receive them.
The text was updated successfully, but these errors were encountered: