@syncfusion/ej2-filemanager
Essential JS 2 FileManager Component
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN license | AI (license): Standard Syncfusion commercial license reference; stable across all their packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Syncfusion packages consistently have link-heavy READMEs; this is a stable false positive across the entire @syncfusion namespace. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 33.2.10 | 10 / 0 | |
| 33.2.6 | 10 / 0 | |
| 33.2.4 | 10 / 0 | |
| 33.2.3 | 10 / 0 | |
| 33.1.47 | 10 / 0 |
v33.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.