@syncfusion/ej2-popups
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 | missing-githead | AI (provenance): Large Syncfusion org publish; missing gitHead appears to be a CI environment change, not a compromise signal. | ai | |
| license | uncommon-license:SEE LICENSE IN license | AI (license): Standard Syncfusion commercial license format; stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-base | AI (dependencies): First-party Syncfusion sibling dependency; same publisher, same versioning scheme, stable pattern across all ej2 packages. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-buttons | AI (dependencies): First-party Syncfusion sibling dependency; same publisher, same versioning scheme, stable pattern across all ej2 packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 33.2.7 | 2 / 0 | |
| 33.2.5 | 2 / 0 | |
| 33.2.3 | 2 / 0 | |
| 32.2.8 | 2 / 0 | |
| 32.2.7 | 2 / 0 | |
| 32.2.6 | 2 / 0 | |
| 32.2.5 | 2 / 0 | |
| 32.2.4 | 2 / 0 | |
| 32.2.3 | 2 / 0 | |
| 32.1.25 | 2 / 0 | |
| 32.1.24 | 2 / 0 | |
| 32.1.19 | 2 / 0 | |
| 31.2.12 | 2 / 0 | |
| 31.2.5 | 2 / 0 |
v33.2.7
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.
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
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.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. 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.
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.