Skip to content

Mitigate the PyPI API token #1306

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

Closed
maresb opened this issue Mar 20, 2025 · 2 comments
Closed

Mitigate the PyPI API token #1306

maresb opened this issue Mar 20, 2025 · 2 comments

Comments

@maresb
Copy link
Contributor

maresb commented Mar 20, 2025

Description

There's currently an API token for PyPI in the secrets that we're no longer using since we migrated to trusted publishing in #1135. (Project admins can see the token here.)

While we could and should delete this token from this repo's secrets, it would be much better if we could deactivate the token first. (Otherwise there's a perpetual risk that the token unexpectedly exists somewhere and could still be compromised.)

As far as I can tell, the only way to figure out the provenance of a PyPI token is for an admin to examine the project's Security history page and look at the logs from before we enabled trusted publishing to see whose account controls the token. (I don't have access.)

CC @twiecki, @fonnesbeck, @michaelosthege

@michaelosthege
Copy link
Member

  • I created the token.
  • Last used 2024-12-03.
  • Removed the token in PyPI
  • Removed the token in GitHub

This should conclude the issue. Let me know if there's anything else I should do :)

@maresb
Copy link
Contributor Author

maresb commented Mar 20, 2025

Perfect, thanks so much @michaelosthege for the rapid and unambiguous response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants