← Home

@syncfusion/ej2-vue-interactive-chat

npm Repository Homepage

Essential JS 2 Component for Vue

8
Versions
SEE LICENSE IN license
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

syncfusionorgessentialjs2syncfusion-javascript

Keywords

vuevuejsej2-vue-aiassistviewvue-aiassistviewej2-vue-interactive-chatvue-interactive-chatassistantopenaiaichatchatbotcopilotai-chatai-chatbotai-assistantai-copilotchatgptgpt4gpt-4conversational-uiconversational-ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Syncfusion packages consistently have link-heavy READMEs; this is a known pattern for their component library, not spam. ai

Versions (showing 8 of 8)

Version Deps Published
33.2.4 3 / 0
33.1.47 3 / 0
32.2.8 3 / 0
32.2.5 3 / 0
32.2.4 3 / 0
32.1.21 3 / 0
31.2.18 3 / 0
31.2.10 3 / 0

v33.1.47

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.

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

v32.2.5

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.

v32.2.4

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.

v32.1.21

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.

v31.2.18

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.

v31.2.10

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.