@tencentcloud/chat-uikit-engine
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tim-upload-plugin | AI (phantom-deps): Optional Tencent plugin referenced in config but not directly imported; stable pattern for this SDK. | ai | |
| phantom-deps | phantom-dep:tim-profanity-filter-plugin | AI (phantom-deps): Optional Tencent plugin referenced in config but not directly imported; stable pattern for this SDK. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.5.8 | 3 / 0 | |
| 2.5.7 | 3 / 0 | |
| 2.5.6 | 3 / 0 | |
| 2.5.5 | 3 / 0 | |
| 2.5.1 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.5 | 3 / 0 |
v2.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.