@syncfusion/ej2-lists
12
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
syncfusionorgessentialjs2syncfusion-javascript
Keywords
ej2Syncfusionweb componentsvirtualizationgroup listcheck listlistview with checkboxlistview templatematerial listui listviewremote listviewnested viewdata listinfinite listsortcheckboxtodolist widgetlist componentmobile listlist gestureses6 listdynamic list
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Consistent with the publisher change; no other suspicious signals. | ai | |
| provenance | no-provenance | AI (provenance): Syncfusion does not publish with Sigstore provenance; stable across versions. | ai | |
| provenance | publisher-changed | AI (provenance): Org-wide transition to syncfusion-javascript account; 230 approved packages under same publisher. | ai | |
| license | uncommon-license:SEE LICENSE IN license | AI (license): Standard Syncfusion commercial license pattern; stable across all their packages. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-popups | AI (phantom-deps): Same-org sibling dep; declared in package.json as a runtime dependency, phantom detection is a false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 34.1.30 | 4 / 0 | |
| 34.1.29 | 4 / 0 | |
| 33.2.3 | 4 / 0 | |
| 33.1.47 | 4 / 0 | |
| 33.1.44 | 4 / 0 | |
| 32.2.7 | 4 / 0 | |
| 32.2.6 | 4 / 0 | |
| 32.2.3 | 4 / 0 | |
| 32.1.24 | 4 / 0 | |
| 32.1.23 | 4 / 0 | |
| 32.1.19 | 4 / 0 | |
| 31.2.12 | 4 / 0 |
v34.1.30
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.29
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.