@syncfusion/ej2-angular-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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Syncfusion publishes synchronized suite releases; gaps between versions are normal for this org's release cadence. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Syncfusion Angular base package; postinstall is a standard Angular schematics/setup script, stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in schematics generator loads same-package lib-details; scoped and benign. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-icons | AI (phantom-deps): Same-org Syncfusion dependency declared in package.json; phantom-dep false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 33.2.9 | 2 / 0 | |
| 33.2.8 | 2 / 0 | |
| 33.2.3 | 2 / 0 | |
| 33.1.46 | 2 / 0 | |
| 32.1.24 | 2 / 0 | |
| 32.1.19 | 2 / 0 |
v33.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.24
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.