← Home

@tencentcloud/trtc-cloud-wx

npm
11
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

rgzhaochengqwallen0809npmyangqtencent-cloud-imashstermileszzhangdawnrkingjiushu530harperhpliujonytangtencent-imxinli123raingxmjasperdaiyilemango2630llwycttateminrychouwei

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Manual publish by known maintainer; no behavioral change vs prior approved version. ai
maintainer-change maintainer-added AI (maintainer-change): Publisher matched as known maintainer on prior versions, not a compromise indicator. ai
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 11 of 11)

Version Deps Published
1.0.10 2 / 0
1.0.9 2 / 0
1.0.8 2 / 0
1.0.7 3 / 0
1.0.6 3 / 0
1.0.5 3 / 0
1.0.4 3 / 0
1.0.3 3 / 0
1.0.2 3 / 0
1.0.1 3 / 0
1.0.0 3 / 0

v1.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mileszzhang → jiushu530 (on 2025-02-18, known maintainer) provenance

This version was published by a different npm account (jiushu530) than the most recent previously approved version (mileszzhang) on 2025-02-18, but jiushu530 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.0.1

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jiushu530.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mileszzhang → jiushu530 (on 2024-12-03, known maintainer) provenance

This version was published by a different npm account (jiushu530) than the most recent previously approved version (mileszzhang) on 2024-12-03, but jiushu530 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.0.0

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.