@syncfusion/ej2-react-calendars
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): syncfusion-javascript is the established Syncfusion org account with 179 approved packages; publisher transition is org-wide, not suspicious. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-base | AI (phantom-deps): Same-org transitive dep; not directly imported but legitimately present as a peer/transitive dependency across all Syncfusion packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Syncfusion packages consistently have marketing-heavy READMEs with many URLs; not a phishing indicator for this established vendor. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 33.2.10 | 3 / 0 | |
| 33.2.8 | 3 / 0 | |
| 33.2.7 | 3 / 0 | |
| 33.2.6 | 3 / 0 | |
| 33.2.5 | 3 / 0 | |
| 33.2.4 | 3 / 0 | |
| 33.2.3 | 3 / 0 | |
| 33.1.44 | 3 / 0 | |
| 32.2.9 | 3 / 0 | |
| 32.2.8 | 3 / 0 | |
| 32.2.7 | 3 / 0 | |
| 32.2.6 | 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.21 | 3 / 0 | |
| 32.1.20 | 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 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.2.7
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. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.25
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. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.1.20
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.19
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.