@syncfusion/ej2-splitbuttons
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Syncfusion does not publish with Sigstore provenance; stable pattern across all their packages. | ai | |
| license | uncommon-license:SEE LICENSE IN license | AI (license): Syncfusion's standard commercial license format; consistent across all their packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 34.1.31 | 2 / 0 | |
| 34.1.29 | 2 / 0 | |
| 33.2.6 | 2 / 0 | |
| 33.2.3 | 2 / 0 | |
| 33.1.49 | 2 / 0 | |
| 33.1.44 | 2 / 0 | |
| 32.2.7 | 2 / 0 | |
| 32.2.3 | 2 / 0 | |
| 32.1.24 | 2 / 0 | |
| 32.1.22 | 2 / 0 | |
| 32.1.19 | 2 / 0 | |
| 31.2.12 | 2 / 0 |
v34.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.