@syncfusion/ej2-react-filemanager
Essential JS 2 FileManager Component for React
14
Versions
SEE LICENSE IN license
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
reactreactjsreact-filemanagerreact-file organizerreact-file organizing toolreact-file pickerreact-file viewerreact-file browserreact-file selectorreact-directory viewerJavaScript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Syncfusion releases in batches; dormancy between release cycles is normal for this org's component packages. | ai | |
| dependencies | unvetted-dep:@syncfusion/ej2-filemanager | AI (dependencies): Same-org core dependency; expected and stable for this React wrapper package across all versions. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-base | AI (phantom-deps): Same-org dep; phantom-dep heuristic fires on indirect usage patterns common in Syncfusion component packages. | ai | |
| provenance | no-provenance | AI (provenance): Syncfusion does not publish with Sigstore provenance; consistent across their entire package portfolio. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 34.1.29 | 3 / 0 | |
| 33.2.13 | 3 / 0 | |
| 33.2.10 | 3 / 0 | |
| 33.2.6 | 3 / 0 | |
| 33.2.4 | 3 / 0 | |
| 33.2.3 | 3 / 0 | |
| 33.1.47 | 3 / 0 | |
| 33.1.45 | 3 / 0 | |
| 33.1.44 | 3 / 0 | |
| 32.2.7 | 3 / 0 | |
| 32.2.3 | 3 / 0 | |
| 32.1.24 | 3 / 0 | |
| 32.1.19 | 3 / 0 | |
| 31.2.12 | 3 / 0 |
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.