← Home

@opentok/client

npm Homepage

The OpenTok.js library lets you use OpenTok-powered video sessions on the web

3
Versions
https://www.vonage.com/legal/communications-apis/terms-of-use/
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

opentok-ownerfrancanoodivorrajoliveraortega

Keywords

tokboxopentokwebrtcvideovideo communicationsreal-time communicationsp2ppeer-to-peerclientsdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/js/opentok.js AI (source-diff): Long strings in dist/ are standard minified bundle output for this SDK; not obfuscated payloads. ai
source-diff encoded-string-file:dist/js/opentok.min.js AI (source-diff): Same as above — minified SDK bundle, not malicious encoding. ai

Versions (showing 3 of 3)

Version Deps Published
2.34.1 0 / 0
2.34.0 0 / 0
2.33.1 0 / 0

v2.34.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.34.0

3 findings
HIGH Long encoded string in modified file: dist/js/opentok.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/js/opentok.min.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.33.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.