@tencentcloud/chat-uikit-engine No license 28 versions

@tencentcloud/chat-uikit-engine

npm Repository

28

Versions

—

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

alsotangwbxl2000xinli123viktorliashfieldfoxashsterdawnrkingbernlaochenximollwyctallen0809npmoriettazimmerfengkyonqijiahaoliangrychouweitateminrgzhao

Keywords

chatreal-time chatmessagingInstant MessagingIMTencent CloudTencent

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	2026/05/22
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	2026/05/22

Versions (showing 28 of 28)

Version	Deps	Published
2.5.8	3 / 0	2025-12-26
2.5.7	3 / 0	2025-10-27
2.5.6	3 / 0	2025-09-19
2.5.5	3 / 0	2025-09-16
2.5.1	3 / 0	2025-07-22
2.5.0	3 / 0	2025-07-08
2.4.5	3 / 0	2025-07-08
2.4.4	3 / 0	2025-04-21
2.4.3	3 / 0	2025-04-21
2.4.2	3 / 0	2025-02-21
2.4.0	3 / 0	2025-01-16
2.3.8	3 / 0	2025-01-10
2.3.6	3 / 0	2024-12-06
2.3.5	3 / 0	2024-12-06
2.3.4	3 / 0	2024-11-22
2.3.3	3 / 0	2024-11-15
2.3.2	3 / 0	2024-10-28
2.3.1	3 / 0	2024-10-25
2.3.0	3 / 0	2024-10-21
2.2.9	3 / 0	2024-10-17
2.2.8	3 / 0	2024-09-24
2.2.7	3 / 0	2024-09-13
2.2.6	3 / 0	2024-09-06
2.2.4	3 / 0	2024-08-02
2.2.3	3 / 0	2024-07-05
2.2.2	3 / 0	2024-06-19
2.2.1	3 / 0	2024-06-17
2.2.0	3 / 0	2024-06-17

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.8

1 finding

LOW No provenance attestation provenance

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

v2.3.6

1 finding

LOW No provenance attestation provenance

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

v2.3.5

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.9

1 finding

LOW No provenance attestation provenance

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

v2.2.8

1 finding

LOW No provenance attestation provenance

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

v2.2.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.

v2.2.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.

v2.2.4

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

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.

v2.2.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.