← Home

@tencentcloud/tui-customer-service-plugin

npm
9
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

mango2630allen0809npmrgzhaojasperdairaingxmtencent-imjonytangchenximojiushu530dawnrkingmileszzhangashstertencent-cloud-imyangq

Keywords

uikitchatuni-appIMtencenttencentcloudmessaging即时通信通信WebSocket

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:dayjs AI (phantom-deps): Config-referenced utility dep, common false positive. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Config-referenced utility dep, common false positive. ai
phantom-deps phantom-dep:@tiptap/pm AI (phantom-deps): Editor framework dep loaded by convention. ai
phantom-deps phantom-dep:@tiptap/core AI (phantom-deps): Editor framework dep loaded by convention. ai
phantom-deps phantom-dep:@types/lodash AI (phantom-deps): Type-only dep, expected to be unimported directly. ai
phantom-deps phantom-dep:vue-clipboard3 AI (phantom-deps): Config-referenced plugin dep. ai
phantom-deps phantom-dep:@tencentcloud/tui-emoji-plugin AI (phantom-deps): Same-org sibling package, expected. ai

Versions (showing 9 of 9)

Version Deps Published
2.2.8 23 / 0
2.2.7 23 / 0
2.2.6 3 / 0
2.2.5 3 / 0
2.2.4 3 / 0
2.2.3 2 / 0
2.2.2 2 / 0
2.2.1 2 / 0
2.2.0 2 / 0

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.5

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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.