@tencentcloud/tuiroom-engine-js
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for bundled packages. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rtc-detect | AI (phantom-deps): Stable false positive; declared dep used in config files, not directly imported — consistent across versions. | ai | |
| phantom-deps | phantom-dep:tcplayer.js | AI (phantom-deps): Stable false positive; declared dep used in config files, not directly imported — consistent across versions. | ai | |
| dependencies | unvetted-dep:tcplayer.js | AI (dependencies): tcplayer.js is Tencent's own media player SDK; expected dependency for this WebRTC room engine package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.2.2 | 4 / 0 | |
| 4.2.1 | 4 / 0 | |
| 4.2.0 | 4 / 0 | |
| 4.1.1 | 4 / 0 | |
| 4.1.0 | 4 / 0 | |
| 4.0.5 | 4 / 0 | |
| 4.0.4 | 4 / 0 | |
| 4.0.3 | 4 / 0 | |
| 4.0.2 | 4 / 0 | |
| 4.0.1 | 4 / 0 | |
| 4.0.0 | 4 / 0 | |
| 3.6.4 | 4 / 0 | |
| 3.6.3 | 4 / 0 | |
| 3.6.2 | 4 / 0 | |
| 3.6.1 | 4 / 0 | |
| 3.6.0 | 4 / 0 | |
| 3.5.2 | 4 / 0 | |
| 3.5.1 | 4 / 0 | |
| 3.5.0 | 4 / 0 | |
| 3.2.4 | 4 / 0 | |
| 3.2.2 | 6 / 27 | |
| 3.0.8 | 4 / 0 |
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
2 findingsPackage 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-10, 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.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.