← Home

@syncfusion/ej2-angular-interactive-chat

npm Repository Homepage

Essential JS 2 Component for Angular

20
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

angularngej2-ng-aiassistviewng-aiassistviewangular-aiassistviewej2-ng-interactive-chatng-interactive-chatej2-angular-interactive-chatassistantopenaiaichatchatbotcopilotai-chatai-chatbotai-assistantai-copilotchatgptgpt4gpt-4conversational-uiconversational-ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:esm2020/src/inline-ai-assist/inlineaiassist.component.mjs AI (source-diff): Long lines are standard Angular ESM bundle output from Syncfusion's build pipeline, not obfuscation. ai
provenance publisher-changed AI (provenance): syncfusion-javascript is the established Syncfusion publisher account with 230 approved packages; org-level transition, not a takeover. ai
dependencies unvetted-dep:@syncfusion/ej2-interactive-chat AI (dependencies): Same-org Syncfusion dependency; consistent pattern across all ej2-angular-* packages. ai
bogus-package bogus-package AI (bogus-package): Syncfusion packages consistently have marketing-heavy READMEs with many URLs; not indicative of spam or phishing. ai
phantom-deps phantom-dep:@syncfusion/ej2-base AI (phantom-deps): Same-org transitive dependency; phantom-dep heuristic is a false positive for this package structure. ai

Versions (showing 20 of 20)

Version Deps Published
33.2.6 3 / 0
33.2.5 3 / 0
33.2.4 3 / 0
33.2.3 3 / 0
33.1.49 3 / 0
33.1.47 3 / 0
33.1.44 3 / 0
32.2.9 3 / 0
32.2.5 3 / 0
32.2.4 3 / 0
32.2.3 3 / 0
32.1.25 3 / 0
32.1.22 3 / 0
32.1.21 3 / 0
32.1.20 3 / 0
31.2.18 3 / 0
31.2.15 3 / 0
31.2.12 3 / 0
31.2.10 3 / 0
31.2.5 3 / 0

v33.2.6

1 finding
LOW No provenance attestation provenance

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

v33.2.5

1 finding
LOW No provenance attestation provenance

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

v33.2.3

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.

v33.1.49

1 finding
LOW No provenance attestation provenance

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

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.

v33.1.44

2 findings
HIGH New obfuscated file: esm2020/src/inline-ai-assist/inlineaiassist.component.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v32.2.9

1 finding
LOW No provenance attestation provenance

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

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

v32.2.3

1 finding
LOW No provenance attestation provenance

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

v32.1.25

1 finding
LOW No provenance attestation provenance

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

v32.1.22

1 finding
LOW No provenance attestation provenance

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

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.

v32.1.20

2 findings
HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2025-12-23) provenance

This version was published by a different npm account than previous versions on 2025-12-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v31.2.18

1 finding
LOW No provenance attestation provenance

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

v31.2.15

1 finding
LOW No provenance attestation provenance

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

v31.2.12

1 finding
LOW No provenance attestation provenance

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

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.

v31.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.