Unverified50% confidenceFactExact time
PyPI implements passwordless publishing based on OIDC through Trusted Publishers, and supports two-factor authentication and signing (such as the attestations introduced by PEP 740).
1
Sources
50%
Confidence
Long-term
Relevance
11/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedPyPI supports Sigstore-signed Trusted Publishing, letting users verify that a distribution package was indeed produced by the project maintainer's CI pipeline.76% similarVerifiedPKCE is a security extension in OAuth 2.1 designed for public clients, where the client submits a hash of the code verifier and must include the original verifier when exchanging for a token, making it impossible to redeem the token even if the authorization code is intercepted.69% similarUnverifiedPKCE was originally designed for public clients that cannot securely store client secrets, and has since been recommended as the default practice for all clients in the OAuth 2.1 draft.66% similarUnverifiedGPG signature verification can confirm that the commit was indeed created by the claimed author and that the content has not been tampered with, but it cannot guarantee code quality or security.63% similarUnverifiedThe double-envelope scheme relies on public key infrastructure (PKI) and strong authentication methods such as smart cards or Mobile-ID.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1183588API
curl https://kongchang.com/api/v1/knowledge/claims/1183588MCP
get_claim(id=1183588)