Pion WebRTC: A pure Go implementation of the WebRTC API (17k stars)
What it does
All text below is quoted directly from the project README.
>A pure Go implementation of the WebRTC API
Features:
- Go implementation of webrtc-pc and webrtc-stats
- DataChannels
- Send/Receive audio and video
- Full ICE Agent
- TURN (UDP, TCP, DTLS and TLS)
- API with direct RTP/RTCP access
- Opus, PCM, H264, VP8 and VP9 packetizer
- Easy integration with x264, libvpx, GStreamer and ffmpeg.
- No Cgo usage
>Go Modules are mandatory for using Pion WebRTC. So make sure you set export GO111MODULE=on, and explicitly specify /v4 (or an earlier version) when importing.
Repository
pion/webrtc
Repository stats
|Metric|Value|
|:-|:-|
|Stars|16,846|
|Forks|1,908|
|Last release|v4.2.24 (2026-10-16)|
|Languages|Go 99.9%|
|Contributors|249|
|AI contributor accounts (Claude / Codex / Cursor / Copilot)|None|
|AI co-authored commits|Claude: 2|
Main contributor
|Field|Value|
|:-|:-|
|Name|Sean DuBois|
|GitHub|@Sean-Der|
|Commits to this repo|750 (top contributor)|
|Company / Location|@pion @webrtc-for-the-curious @glimesh / Columbus, OH|
|Website|siobud.com|
|X / Twitter|@_pion|
|Followers|1276|
|Public repos|90|
|On GitHub since|2012-01-03|
------------------------------------------------------------------------------------------------
Discover the best GitHub repos without the endless scrolling.
Get top repos organized by category (AI, DevOps, Databases & more), plus key takeaways from developers' most useful comments - all in one free, twice-weekly newsletter.
👉 Get the best repos & community insights - Free
11 points
Tell HN: Anthropic found 36 bugs (6 CVEs) in Pion, OpenAI missed them
We added Pion DTLS to Anthropic's OSS scanner last week (oss-scanner#93), and today we woke up to a report with 36 bugs, including 6 security vulnerabilities: 2 critical, 3 high, and 1 moderate. Four of them affect WebRTC.
Some of these vulnerabilities have been sitting in the codebase for over 4 years, surviving years of testing and security scans. It's funny that our inboxes are constantly spammed with AI-generated security reports from people using Codex and Claude, most of which flag pointless issues. Yet somehow, none of them caught these.
The funniest part? Anthropic also found 3 bugs that OpenAI's internal code review missed. I had asked OpenAI to review a new DTLS API since they use Pion and had a use case for it in SPED. Their review didn't flag any bugs. Anthropic found an authentication issue, a deadlock, and a TLS KeyUpdate bug (Maybe their model ignored this one because it's not a WebRTC issue). Luckily, the API hasn't been released yet. The fixes: dtls#1236
Here are the security advisories for the CVEs Anthropic found (all of them are pre-chatgpt!):
Critical: DTLS handshake signature confusion allows peer impersonation - github.com/pion/dtls/security/advisories/GHSA-7c2…
Critical: Client authentication bypass through premature session caching - github.com/pion/dtls/security/advisories/GHSA-hhp…
High: Client authentication bypass with shared session stores - github.com/pion/dtls/security/advisories/GHSA-cqh…
High: Unbounded handshake cache allows remote memory exhaustion - github.com/pion/dtls/security/advisories/GHSA-jm5…
High: Oversized RSA keys allow CPU exhaustion - github.com/pion/dtls/security/advisories/GHSA-jp2…
Moderate: Repeated certificate verification allows CPU exhaustion - github.com/pion/dtls/security/advisories/GHSA-qpg…
The most annoying part is that neither company's models were willing to help with verifying or filtering the bugs, so we had to manually review them one by one (Spent all day :/
8 points · 8 comments
Mentions
Pion WebRTC: A pure Go implementation of the WebRTC API (17k stars) What it does All text below is quoted directly from the project README. >A pure Go implementation of the WebRTC API Features: - Go implementation of webrtc-pc and webrtc-stats - DataChannels - Send/Receive audio and video - Full ICE Agent - TURN (UDP, TCP, DTLS and TLS) - API with direct RTP/RTCP access - Opus, PCM, H264, VP8 and VP9 packetizer - Easy integration with x264, libvpx, GStreamer and ffmpeg. - No Cgo usage >Go Modules are mandatory for using Pion WebRTC. So make sure you set export GO111MODULE=on, and explicitly specify /v4 (or an earlier version) when importing. Repository pion/webrtc Repository stats |Metric|Value| |:-|:-| |Stars|16,846| |Forks|1,908| |Last release|v4.2.24 (2026-10-16)| |Languages|Go 99.9%| |Contributors|249| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|None| |AI co-authored commits|Claude: 2| Main contributor |Field|Value| |:-|:-| |Name|Sean DuBois| |GitHub|@Sean-Der| |Commits to this repo|750 (top contributor)| |Company / Location|@pion @webrtc-for-the-curious @glimesh / Columbus, OH| |Website|siobud.com| |X / Twitter|@_pion| |Followers|1276| |Public repos|90| |On GitHub since|2012-01-03| ------------------------------------------------------------------------------------------------ Discover the best GitHub repos without the endless scrolling. Get top repos organized by category (AI, DevOps, Databases & more), plus key takeaways from developers' most useful comments - all in one free, twice-weekly newsletter. 👉 Get the best repos & community insights - Free
Tell HN: Anthropic found 36 bugs (6 CVEs) in Pion, OpenAI missed them We added Pion DTLS to Anthropic's OSS scanner last week (oss-scanner#93), and today we woke up to a report with 36 bugs, including 6 security vulnerabilities: 2 critical, 3 high, and 1 moderate. Four of them affect WebRTC. Some of these vulnerabilities have been sitting in the codebase for over 4 years, surviving years of testing and security scans. It's funny that our inboxes are constantly spammed with AI-generated security reports from people using Codex and Claude, most of which flag pointless issues. Yet somehow, none of them caught these. The funniest part? Anthropic also found 3 bugs that OpenAI's internal code review missed. I had asked OpenAI to review a new DTLS API since they use Pion and had a use case for it in SPED. Their review didn't flag any bugs. Anthropic found an authentication issue, a deadlock, and a TLS KeyUpdate bug (Maybe their model ignored this one because it's not a WebRTC issue). Luckily, the API hasn't been released yet. The fixes: dtls#1236 Here are the security advisories for the CVEs Anthropic found (all of them are pre-chatgpt!): Critical: DTLS handshake signature confusion allows peer impersonation - github.com/pion/dtls/security/advisories/GHSA-7c2… Critical: Client authentication bypass through premature session caching - github.com/pion/dtls/security/advisories/GHSA-hhp… High: Client authentication bypass with shared session stores - github.com/pion/dtls/security/advisories/GHSA-cqh… High: Unbounded handshake cache allows remote memory exhaustion - github.com/pion/dtls/security/advisories/GHSA-jm5… High: Oversized RSA keys allow CPU exhaustion - github.com/pion/dtls/security/advisories/GHSA-jp2… Moderate: Repeated certificate verification allows CPU exhaustion - github.com/pion/dtls/security/advisories/GHSA-qpg… The most annoying part is that neither company's models were willing to help with verifying or filtering the bugs, so we had to manually review them one by one (Spent all day :/
😳 想做音视频通话,WebRTC 底层 C++ 改不动。pion/webrtc 1.6 万星,纯 Go 实现,不碰 C++ 就能接进自己后端,会议和直播都能做。 pion/webrtc