Skip to content

Mitigate the PyPI API token #435

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

Open
maresb opened this issue Mar 20, 2025 · 0 comments
Open

Mitigate the PyPI API token #435

maresb opened this issue Mar 20, 2025 · 0 comments

Comments

@maresb
Copy link
Collaborator

maresb commented Mar 20, 2025

(See also: pymc-devs/pytensor#1306)

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 #409. (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.)

I can see that this token is associated with @fonnesbeck's account, so I'd recommend disabling that token (as well as ensuring that all other projects are migrated to trusted publishing and deleting those tokens too).

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

1 participant