← Home

@syncfusion/ej2-angular-charts

npm Repository Homepage

Feature-rich chart control with built-in support for over 25 chart types, technical indictors, trendline, zooming, tooltip, selection, crosshair and trackball. for Angular

26
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

angularangular-chartsangular-accumulation-chartangular-pie-chartangular-stock-chartangular-rangenavigatorangular-rangeselectorangular-sparklineangular-sparkline-chartangular-smith-chartangular-bullet-chartangular-bullet-graphangular-chart3dangular-circularchart3dangular-sankey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:esm2020/src/sankey/links.directive.mjs AI (source-diff): Angular compiler metadata produces long single lines; code is readable and benign Sankey directive. ai
source-diff obfuscated-file:esm2020/src/sankey/nodes.directive.mjs AI (source-diff): Angular compiler metadata produces long single lines; code is readable and benign Sankey directive. ai
source-diff obfuscated-file:esm2020/src/sankey/sankey-all.module.mjs AI (source-diff): Angular compiler metadata produces long single lines; code is readable and benign NgModule definition. ai
source-diff obfuscated-file:esm2020/src/sankey/sankey.component.mjs AI (source-diff): Angular compiler metadata produces long single lines; code is readable and benign Sankey component. ai
provenance publisher-changed AI (provenance): Syncfusion org account migration; syncfusion-javascript has 178 approved packages across the same scope. ai
phantom-deps phantom-dep:@syncfusion/ej2-base AI (phantom-deps): Same-org transitive dep; phantom-dep false positive for this package family. ai

Versions (showing 26 of 26)

Version Deps Published
33.2.10 3 / 0
33.2.8 3 / 0
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.8 3 / 0
32.2.7 3 / 0
32.2.5 3 / 0
32.2.4 3 / 0
32.2.3 3 / 0
32.1.25 3 / 0
32.1.24 3 / 0
32.1.23 3 / 0
32.1.22 3 / 0
32.1.19 3 / 0
31.2.18 3 / 0
31.2.16 3 / 0
31.2.15 3 / 0
31.2.12 3 / 0
31.2.10 3 / 0
31.2.5 3 / 0

v33.2.10

1 finding
LOW No provenance attestation provenance

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

v33.2.8

1 finding
LOW No provenance attestation provenance

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

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

v33.1.49

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

5 findings
HIGH New obfuscated file: esm2020/src/sankey/links.directive.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.

HIGH New obfuscated file: esm2020/src/sankey/nodes.directive.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.

HIGH New obfuscated file: esm2020/src/sankey/sankey-all.module.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.

HIGH New obfuscated file: esm2020/src/sankey/sankey.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.

v33.1.44

5 findings
HIGH New obfuscated file: esm2020/src/sankey/links.directive.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.

HIGH New obfuscated file: esm2020/src/sankey/nodes.directive.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.

HIGH New obfuscated file: esm2020/src/sankey/sankey-all.module.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.

HIGH New obfuscated file: esm2020/src/sankey/sankey.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.8

1 finding
LOW No provenance attestation provenance

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

v32.2.7

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

1 finding
LOW No provenance attestation provenance

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

v32.1.23

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

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

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

This version was published by a different npm account than previous versions on 2025-12-16. 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.16

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