← Home

@tencentcloud/trtc-cloud-wx

npm
4
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-imxinli123raingxmjasperdaiyilemango2630llwycttateminrychouwei

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Established Tencent Cloud org package with 60 versions; sparse metadata is typical for corporate SDK wrappers. ai
npm-metadata no-description AI (npm-metadata): Corporate SDK; missing description is cosmetic, not a risk signal here. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.9 2 / 0
1.0.8 2 / 0
1.0.7 3 / 0
1.0.6 3 / 0

v1.0.9

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.

v1.0.8

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.

v1.0.7

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.

v1.0.6

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.