Helping the PyTorch Community Improve the Security Posture of th...
summary
PyTorch moves under Linux Foundation governance, adopts OpenSSF best practices, and hardens dependency management after a malicious pip package in 2022 and later findings of dependency and RCE risks and model‑poisoning vectors. Contribution mix shifts to 60% Meta 40% community, tooling adds debugging/inspection for third‑party libs, and a new collaboration with Google forms CoAI (Coalition for secure artificial intelligence) to focus on software supply‑chain security, defender preparedness, and AI risk governance.
AI-written summary · about
chapters (9)
- 0:00PyTorch security session
- 2:51Government on open source security
- 8:03AI ecosystem control concerns
- 13:00PyTorch governance model
- 15:23Recent PyTorch security incidents
- 20:35Introducing Coalition for Secure AI
- 27:19Call to action for security
- 31:01IBM's open source and AI strategy
- 38:47Conclusion
related talks
09mOpening Remarks
48mFireside Chat
21mNavigating the Intersection: AI’s Role in Shaping the Secure Open Source Software Ecos...
18mThe State of the PyTorch Ecosystem in 2026: Global Trends and China’s Rising Role
06mCommunity Updates
10mPyTorch CTO
29mCheese Must Stand: Defending the Python Library Ecosystem in 2025
12mKeynote: How PyTorch Became the Foundation of the AI Revolution