upvote
> This shows they're not just, IDK, bowing to Microsoft's demands.

Not only don't we, but I must emphasize that Microsoft did not pay for anything involving the implementation of either Trusted Publishing or attestations on PyPI. I wrote a personal blog post explaining some of my own rationale for why we prioritized GitHub and GitLab for PyPI's initial support targets, and it shouldn't be surprising to anybody who knows me that the reasons are pragmatic, not dogmatic[1].

[1]: https://blog.yossarian.net/2024/11/18/Security-means-securin...

reply
Is "a public key that I personally upload to my PyPI account, using the credentials you already have that allow me to use that account" on the list of targets that will ever be supported?

If not--i.e., if only recognized "forges" are ever going to be supported--why not?

reply
reply
Thanks, I'll comment further in that subthread.
reply
All absolutely reasonable. At the same time though there are a lot of roads leading to centralisation, and as they all converge it gets just a bit .. problematic.

Absolutely not claiming its not a pragmatic step, but equal-footing alternatives would be useful.

I'm no tin-foil-hat - but when a website account requires government id (like in the uk), and creating software requires signing by the website, you link all the things - is that a good outcome?

reply
This is true, and it’s why I’m hopeful that some of the newer forges can make meaningful default posture improvements that make migration away from centralized services the dispassionate choice to a user who cares about availability and security.
reply