How to Become a Member of the Python Security Response Team

<h2>Introduction</h2> <p>Security doesn't happen by accident. The Python Security Response Team (PSRT) is the volunteer and staff group that triages vulnerability reports, coordinates fixes, and keeps the Python ecosystem safe. Recently, thanks to the work of Security Developer-in-Residence Seth Larson, the PSRT has adopted PEP 811—a public governance document that brings transparency to team membership, responsibilities, and onboarding. This guide walks you through becoming a member of the PSRT, using the new, approved process that balances security needs with sustainability.</p><figure style="margin:20px 0"><img src="https://picsum.photos/seed/2174506636/800/450" alt="How to Become a Member of the Python Security Response Team" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px"></figcaption></figure> <h2>What You Need</h2> <ul> <li><strong>Existing involvement</strong> in Python security or related open-source projects (e.g., CPython, pip, PyPI).</li> <li><strong>Nomination</strong> by a current PSRT member.</li> <li><strong>At least ⅔ (two‑thirds)</strong> of positive votes from existing PSRT members.</li> <li><strong>No requirement</strong> to be a core developer, team member, or triager—anyone with relevant expertise can be considered.</li> <li><strong>Understanding</strong> of PSRT responsibilities: triaging reports, coordinating with project maintainers, and handling embargoed disclosures.</li> </ul> <h2>Step-by-Step Guide</h2> <h3>Step 1: Learn About the PSRT and Its Role</h3> <p>Before pursuing membership, familiarize yourself with the team’s mission. The PSRT handles all security vulnerability reports for CPython, pip, and other core Python projects. They coordinate with maintainers, ensure fixes adhere to API conventions and threat models, and sometimes work with other open-source projects (e.g., the recent ZIP archive differential attack mitigation on PyPI). Read the <a href="https://peps.python.org/pep-0811/" target="_blank" rel="noopener">PEP 811 governance document</a> to understand the structure and expectations.</p> <h3>Step 2: Gain Relevant Experience</h3> <p>While you don’t need to be a core developer, you should have a track record in security work. This could include:</p> <ul> <li>Reporting vulnerabilities to the PSRT or other projects.</li> <li>Contributing to security fixes or audits.</li> <li>Participating in security discussions on Python issue trackers or security mailing lists.</li> <li>Collaborating with maintainers on security-related improvements.</li> </ul> <p>The PSRT encourages involvement from non‑core contributors; expertise matters more than formal titles.</p> <h3>Step 3: Find a Nominator</h3> <p>You need a current PSRT member to nominate you. The <a href="https://www.python.org/psrt/" target="_blank" rel="noopener">public list of members</a> is now available. Reach out to a member you know, demonstrate your interest and experience, and request their support. The nominator will initiate the onboarding process defined in PEP 811.</p> <h3>Step 4: Go Through the Voting Process</h3> <p>After nomination, the existing PSRT members vote. You must receive at least two‑thirds positive votes to be accepted. The vote is confidential to protect security considerations. If approved, you will be added to the team roster and receive access to private communication channels and vulnerability tracking tools.</p> <h3>Step 5: Complete Onboarding and Start Contributing</h3> <p>New members go through a documented onboarding process that covers:</p> <ul> <li>PSRT procedures for triaging and disclosing vulnerabilities.</li> <li>Use of GitHub Security Advisories and other coordination tools.</li> <li>Ethics, confidentiality, and sustainability practices.</li> </ul> <p>After onboarding, you can begin triaging reports, coordinating with experts, and helping to publish advisories. The PSRT also records contributors in CVEs and OSV records to give proper recognition—something Seth Larson and Jacob Coffee (the first non‑Release Manager member since 2023) are actively improving.</p> <h2>Tips for Success</h2> <ul> <li><strong>Start small</strong> – Engage with the Python security community by attending open meetings, subscribing to the security‑announce list, or helping with documented vulnerability reviews.</li> <li><strong>Build relationships</strong> – Many nominations come from existing team members who know your work. Contribute to security fixes or participate in discussions to become visible.</li> <li><strong>Emphasize sustainability</strong> – The PSRT values long‑term maintainability of fixes and minimal disruption to users. Highlight your ability to consider those aspects.</li> <li><strong>Be patient</strong> – The voting process may take time. The team balances security with transparency; trust the process.</li> <li><strong>Celebrate contributions</strong> – Security work often goes unrecognized. The PSRT now explicitly credits reporters, coordinators, and reviewers. Make sure you’re prepared to give that same recognition to others.</li> </ul> <p>With the new governance in place, joining the PSRT is more transparent and accessible. The first new member (Jacob Coffee) has already on‑boarded, proving the process works. If you have the skills and dedication, you can help keep the Python ecosystem secure.</p>