Gathering detailed insights and metrics for webrtc-adapter
Gathering detailed insights and metrics for webrtc-adapter
Gathering detailed insights and metrics for webrtc-adapter
Gathering detailed insights and metrics for webrtc-adapter
webrtc-adapter-test
Hide browser differences in WebRTC APIs (test package name)
@teravoz/react-webrtc-adapter
The Teravoz WebRTC Adapter for wrapping up your React componponents with telephonic capabilities
webrtc-internals-adapter
webrtc-internals anywhere
@allex/webrtc-adapter
A shim to insulate apps from WebRTC spec changes and browser prefix differences
Shim to insulate apps from spec changes and prefix differences. Latest adapter.js release:
npm install webrtc-adapter
Typescript
Module System
Min. Node Version
Node Version
NPM Version
99.1
Supply Chain
94.4
Quality
83.7
Maintenance
100
Vulnerability
100
License
JavaScript (99.88%)
HTML (0.12%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
BSD-3-Clause License
3,708 Stars
3,088 Commits
858 Forks
165 Watchers
7 Branches
74 Contributors
Updated on Jul 05, 2025
Latest Version
9.0.3
Package Id
webrtc-adapter@9.0.3
Unpacked Size
523.09 kB
Size
99.94 kB
File Count
36
NPM Version
10.8.2
Node Version
20.19.0
Published on
Apr 18, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
25
adapter.js is a shim to insulate apps from spec changes and prefix differences in WebRTC. The prefix differences are mostly gone these days but differences in behaviour between browsers remain.
This repository used to be part of the WebRTC organisation on github but moved. We aim to keep the old repository updated with new releases.
1npm install webrtc-adapter
1bower install webrtc-adapter
Just import adapter:
import adapter from 'webrtc-adapter';
No further action is required. You might want to use adapters browser detection which detects which webrtc quirks are required. You can look at
adapter.browserDetails.browser
for webrtc engine detection (which will for example detect Opera or the Chromium based Edge as 'chrome') and
adapter.browserDetails.version
for the version according to the user-agent string.
Copy to desired location in your src tree or use a minify/vulcanize tool (node_modules is usually not published with the code). See webrtc/samples repo as an example on how you can do this.
In the gh-pages branch prebuilt ready to use files can be downloaded/linked directly. Latest version can be found at https://webrtc.github.io/adapter/adapter-latest.js. Specific versions can be found at https://webrtc.github.io/adapter/adapter-N.N.N.js, e.g. https://webrtc.github.io/adapter/adapter-1.0.2.js.
You will find adapter.js
in bower_components/webrtc-adapter/
.
In node_modules/webrtc-adapter/out/ folder you will find 4 files:
adapter.js
- includes all the shims and is visible in the browser under the global adapter
object (window.adapter).adapter_no_global.js
- same as adapter.js
but is not exposed/visible in the browser (you cannot call/interact with the shims in the browser).Include the file that suits your need in your project.
Head over to test/README.md and get started developing.
patch
, minor
or major
in place of <version>
. Run npm version <version> -m 'bump to %s'
and type in your password lots of times (setting up credential caching is probably a good idea).git pull
npm publish
(you need access to the webrtc-adapter npmjs package). For big changes, consider using a tag version such as next
and then change the dist-tag after testing.Note: Currently only tested on Linux, not sure about Mac but will definitely not work on Windows.
In some cases it may be necessary to do a patch version while there are significant changes changes on the master branch. To make a patch release,
git checkout tags/vMajor.minor.patch
.git cherry-pick some-commit-hash
.npm version patch
. This will create a new patch version and publish it on github.origin/bumpVersion
branch and publish the new version using npm publish
.No vulnerabilities found.
Reason
9 commit(s) out of 30 and 6 issue activity out of 30 found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
no vulnerabilities detected
Reason
no binaries found in the repo
Reason
dependency not pinned by hash detected -- score normalized to 9
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
GitHub code reviews found for 16 commits out of the last 30 -- score normalized to 5
Details
Reason
no badge detected
Reason
non read-only tokens detected in GitHub workflows
Details
Reason
security policy file not detected
Reason
project is not fuzzed
Score
Last Scanned on 2022-08-15
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More