PyPI Expands Trusted Publishing to GitLab Self-Managed as Adoption Passes 25 Percent
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads
- Sarah Gooding

The Python Package Index (PyPI) has expanded its Trusted Publishing feature to support GitLab Self-Managed instances, as usage of the security mechanism continues to grow across the ecosystem.
According to PyPI, about one-quarter of all files uploaded to the registry in October 2025 were published via Trusted Publishing. That’s up from roughly 10 percent in early 2024. More than 45,000 projects have now enabled the feature since it was introduced in 2023.

Trusted Publishing lets CI platforms publish packages to PyPI without storing permanent API tokens. Instead, PyPI issues short-lived, scoped tokens to a verified build system through an OpenID Connect (OIDC) trust relationship. The approach has been adopted by major providers like GitHub Actions and GitLab.com, reducing the risk of token leaks and impersonation in package supply chains.
GitLab Self-Managed Enters Beta
#The latest update extends this model to self-hosted GitLab deployments, allowing organizations that run their own GitLab instances to participate in the beta. During the trial period, PyPI staff must manually onboard each instance to validate different configurations before wider availability.
Trusted Publishing for GitLab.com has been stable since early 2024, but self-managed support was a long-requested feature for enterprises that maintain private infrastructure or compliance-restricted environments.
Organization-Level Ownership and Governance
#PyPI Organizations also gain finer control over project ownership. Previously, if a user created a pending trusted publisher for a project that didn’t yet exist, that individual automatically became the project owner once it was uploaded. With the new workflow, organizations can create pending publishers at the org level, ensuring the resulting project is owned by the organization itself rather than a single maintainer.
The change helps prevent ownership drift in multi-maintainer environments and simplifies management of large organizational namespaces on PyPI.
Renewed Support for Python Infrastructure
#The update comes at a moment of renewed community energy around the Python Software Foundation (PSF). In late October, the PSF announced it would withdraw from a $1.5M U.S. National Science Foundation grant opportunity after being presented with new conditions that required recipients to certify they do not operate programs that “advance or promote DEI.” Those terms would have applied to all PSF activities during the grant period and included potential claw-backs for noncompliance. The PSF board voted unanimously to decline the funding, saying the conditions conflicted with its mission to support a diverse and international Python community:
We’re disappointed to have been put in the position where we had to make this decision, because we believe our proposed project would offer invaluable advances to the Python and greater open source community, protecting millions of PyPI users from attempted supply-chain attacks. The proposed project would create new tools for automated proactive review of all packages uploaded to PyPI, rather than the current process of reactive-only review. These novel tools would rely on capability analysis, designed based on a dataset of known malware.
In the two weeks following that announcement, the organization received more than $160,000 in donations from nearly 2,000 individual donors, including 313 new members. Community members quickly launched a matching campaign that raised $34,000 in support of sustaining Python’s shared infrastructure.

That infrastructure includes PyPI and the ongoing work to improve software supply chain security across the Python ecosystem. As adoption of Trusted Publishing continues to climb, the PSF’s ability to maintain and expand these initiatives will rely on the same collective support that rallied so quickly around the foundation this month.
In a recent post titled "Open Infrastructure is Not Free," the PSF described the growing strain of maintaining PyPI’s infrastructure, which now handles between 2 and 3 billion requests per day with a small staff funded largely by the foundation’s general budget. The PSF described the situation as a “critical inflection point” for PyPI’s long-term sustainability and outlined plans to pursue multi-year infrastructure partnerships and optional paid features for organizations that publish heavily to PyPI.




