@tencentcloud/tuiroom-engine-electron
TUIRoomEngine Electron SDK
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Tencent Cloud SDK with documented repo; provenance absence is common and not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:rtc-detect | AI (dependencies): Known Tencent RTC utility package; stable dependency across versions of this SDK. | ai | |
| dependencies | unvetted-dep:trtc-electron-sdk | AI (dependencies): First-party Tencent TRTC Electron SDK; expected core dependency for this package. | ai | |
| dependencies | unvetted-dep:@tencentcloud/chat | AI (dependencies): First-party Tencent Cloud Chat SDK; expected dependency for this room engine package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 3 / 0 | |
| 4.1.1 | 3 / 0 | |
| 4.0.6 | 3 / 0 | |
| 4.0.1 | 3 / 0 | |
| 3.6.1 | 3 / 0 | |
| 3.2.4 | 3 / 0 | |
| 1.7.11 | 3 / 0 |
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (allen0809npm) than the most recent previously approved version (xinli123) on 2026-02-04, but allen0809npm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.