trtc-sdk-v5
Tencent Cloud RTC SDK for Web
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:plugins/device-detector/device-detector.umd.js | AI (source-diff): Bundled UMD build output, minified not obfuscated. | ai | |
| source-diff | encoded-string-file:plugins/device-detector/device-detector.esm.js | AI (source-diff): Base64 audio asset (test sound) embedded in UI component, benign. | ai | |
| source-diff | encoded-string-file:assets/audioProcessor-wasm.js | AI (source-diff): Emscripten-generated WASM loader boilerplate, not hidden payload. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): WASM codec/denoiser binaries are core to a media SDK's stated function. | ai | |
| source-diff | obfuscated-file:plugins/cdn-streaming/cdn-streaming.js | AI (source-diff): Bundled minified plugin output, not obfuscation; part of official Tencent SDK plugin set. | ai | |
| source-diff | net-exec-file:plugins/video-effect/virtual-background/virtual-background.esm.js | AI (source-diff): fetch() targets Tencent's own rtc.qq.com API; dynamic-require is emscripten boilerplate, not a loader. | ai | |
| source-diff | net-exec-file:plugins/video-effect/virtual-background/virtual-background.iife.js | AI (source-diff): Same first-party bundled plugin, duplicate build format. | ai | |
| phantom-deps | phantom-dep:afsm | AI (phantom-deps): Bundled/minified SDK code has no scannable imports; dep matches RTC SDK function. | ai | |
| source-diff | net-exec-file:plugins/ai-denoiser/denoiser-wasm.js | AI (source-diff): Standard emscripten runtime pattern, not a dropper/loader. | ai | |
| phantom-deps | phantom-dep:sdp-transform | AI (phantom-deps): Bundled/minified SDK code has no scannable imports; dep matches RTC SDK function. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Bundled/minified SDK code has no scannable imports; dep matches RTC SDK function. | ai | |
| phantom-deps | phantom-dep:webrtc-adapter | AI (phantom-deps): Bundled/minified SDK code has no scannable imports; dep matches RTC SDK function. | ai | |
| source-diff | obfuscated-file:plugins/ai-denoiser/denoiser-wasm.js | AI (source-diff): Emscripten WASM loader boilerplate for audio denoiser plugin, not malicious obfuscation. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.19.0 | 1 / 0 | |
| 5.18.3 | 1 / 0 | |
| 5.18.2 | 1 / 0 | |
| 5.18.1 | 1 / 0 | |
| 5.18.0 | 1 / 0 | |
| 5.17.1 | 1 / 0 | |
| 5.17.0 | 1 / 0 | |
| 5.16.0 | 1 / 0 | |
| 5.15.2 | 1 / 0 | |
| 5.15.1 | 1 / 0 | |
| 5.15.0 | 1 / 0 | |
| 5.14.1 | 1 / 0 | |
| 5.14.0 | 1 / 0 | |
| 5.4.2 | 1 / 0 | |
| 5.4.1 | 1 / 0 | |
| 5.4.0 | 1 / 0 | |
| 5.3.2 | 1 / 0 | |
| 5.1.3 | 1 / 0 | |
| 5.1.2 | 1 / 0 | |
| 5.1.1 | 4 / 0 | |
| 5.1.0 | 4 / 0 | |
| 5.0.3 | 0 / 0 | |
| 5.0.2 | 0 / 0 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 |
v5.19.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.3
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.2
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.1
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.0
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.1
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.0
2 findingsPackage contains compiled binaries that could be backdoors: • assets/videodec_simd.wasm • assets/videodec.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.