@tencentcloud/call-engine-js
Tencent Cloud TUICallEngine SDK for Web
1
Versions
ISC
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
rgzhaoallen0809npmyangqtencent-cloud-imashstermileszzhangdawnrkingjiushu530chenximoharperhpliujonytangtencent-imraingxmjasperdaiyilemango2630llwycttateminrychouwei
Keywords
callvideo callaudio callvideoaudioTRTCcameramicrophonewebrtcreal-time communicationjavascriptrtc
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in minified bundle at regenerator-runtime boilerplate; standard transpilation artifact for this SDK. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill injected at build time; not directly imported but legitimately used. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Bundled into CJS output; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:tuikit-logger | AI (phantom-deps): Referenced in config; consistent with Tencent internal tooling pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.3.4 | 6 / 0 |
v3.3.4
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.