@syncfusion/ej2-base
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in the obfuscated license CLI binary; consistent with Syncfusion's license-check tooling across all versions. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-icons | AI (phantom-deps): @syncfusion/ej2-icons is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Inside obfuscated license CLI; stable pattern for this package. | ai | |
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): Syncfusion license-validation CLI; obfuscated intentionally, stable across versions. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Template engine pattern in src/template.js; standard for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Internal Selenium test address in e2e config; not runtime code. | ai | |
| semgrep | semgrep:obfuscation-hex-functions | AI (semgrep): Same obfuscated license CLI; stable pattern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 33.2.3 | 1 / 0 | |
| 33.1.45 | 1 / 0 | |
| 33.1.44 | 1 / 0 | |
| 32.2.9 | 1 / 0 | |
| 32.2.6 | 1 / 0 | |
| 32.2.3 | 1 / 0 | |
| 32.1.24 | 1 / 0 | |
| 32.1.23 | 1 / 0 | |
| 32.1.22 | 1 / 0 | |
| 32.1.19 | 1 / 0 | |
| 31.2.18 | 1 / 0 | |
| 31.2.12 | 1 / 0 | |
| 31.2.5 | 1 / 0 |
v33.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: syncfusion-javascript.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.