← Home

@syncfusion/ej2-filemanager

npm Repository Homepage

Essential JS 2 FileManager Component

15
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

ej2syncfusionJavaScriptTypeScriptfilemanagerfile organizerfile organizing toolfile pickerfile viewerfile browserfile selectordirectory viewer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:SEE LICENSE IN license AI (license): Standard Syncfusion commercial license reference; stable across all their packages. ai
bogus-package bogus-package AI (bogus-package): Syncfusion packages consistently have link-heavy READMEs; this is a stable false positive across the entire @syncfusion namespace. ai

Versions (showing 15 of 15)

Version Deps Published
34.1.31 10 / 0
34.1.29 10 / 0
33.2.13 10 / 0
33.2.10 10 / 0
33.2.6 10 / 0
33.2.4 10 / 0
33.2.3 10 / 0
33.1.47 10 / 0
33.1.45 10 / 0
33.1.44 10 / 0
32.2.7 10 / 0
32.2.3 10 / 0
32.1.24 10 / 0
32.1.19 10 / 0
31.2.12 10 / 0

v34.1.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v34.1.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v33.1.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v33.1.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.1.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.1.19

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.