Strengthening Python Security: Inside the PSRT's New Governance and Growing Team

Introduction

The Python Security Response Team (PSRT) has long played a critical role in safeguarding the Python ecosystem. Recent developments, including the approval of a formal governance document (PEP 811) and the addition of a new team member, signal a renewed commitment to transparency and sustainability in security operations. This article explores these changes, the team's responsibilities, and how interested contributors can get involved.

Strengthening Python Security: Inside the PSRT's New Governance and Growing Team

Governance and Transparency: PEP 811

Thanks to the efforts of Seth Larson, the Python Security Developer-in-Residence, the PSRT now operates under a publicly documented governance structure outlined in PEP 811. This document clarifies the team's relationship with the Python Steering Council and establishes clear processes for member onboarding, offboarding, and responsibilities. For the first time, the PSRT publishes a public list of members, ensuring transparency while balancing security needs and team sustainability.

Key Elements of the New Governance

Public membership list: All current PSRT members are now listed openly.
Defined roles: Responsibilities for both members and administrators are explicitly documented.
Onboarding/offboarding process: A structured procedure ensures smooth transitions and maintains team expertise.
Steering Council alignment: Formal guidelines define how the PSRT interacts with the Python Steering Council.

Growing the Team: New Member Onboarding

The new governance is already yielding results. Jacob Coffee, the PSF Infrastructure Engineer, has joined the PSRT—the first new non-Release Manager member since Seth Larson joined in 2023. This addition strengthens the team's capacity to handle vulnerabilities and ensures long-term sustainability of Python security efforts. Additional members are expected to join in the coming months, further bolstering the team's expertise.

What Does the PSRT Do?

Security does not happen by accident. The PSRT works tirelessly—often behind the scenes—to triage and coordinate vulnerability reports and remediations. In the past year alone, the team published 16 vulnerability advisories for CPython and pip, the highest annual number to date.

Collaboration with Experts

The PSRT rarely works in isolation. Coordinators actively involve project maintainers and subject-matter experts during the remediation process. This collaborative approach ensures fixes adhere to existing API conventions, follow established threat models, remain maintainable over time, and minimize disruption for users.

Cross-Project Coordination

Sometimes vulnerabilities affect multiple open-source projects. The PSRT coordinates with other maintainers to avoid surprising the ecosystem with simultaneous advisories. A notable example was the mitigation of PyPI's ZIP archive differential attack, where cross-team collaboration prevented widespread impact.

Recognizing Contributions

Security work deserves the same recognition as code commits or documentation updates. Seth Larson and Jacob Coffee are developing improvements to GitHub Security Advisories workflows. These enhancements will ensure that reporters, coordinators, and remediation developers are properly credited in CVE and OSV records, acknowledging their otherwise private contributions.

How to Join the Python Security Response Team

If you are interested in directly contributing to Python's security, the path is now clearer than ever. The nomination process mirrors the Core Team nomination procedure:

An existing PSRT member must nominate you.
Your nomination requires at least ⅔ positive votes from current PSRT members.

You do not need to be a core developer, team member, or triager to qualify. The PSRT values diverse expertise and perspectives. If you are passionate about software security and the Python ecosystem, consider reaching out to a current member to discuss a nomination.

Conclusion

The Python Security Response Team's new governance structure and growing membership represent important strides toward a more secure and sustainable open-source ecosystem. With clearer processes, enhanced transparency, and a focus on collaboration, the PSRT is better equipped than ever to protect Python users worldwide. Whether you are a seasoned security expert or an enthusiastic contributor, there has never been a better time to get involved.

Tags: