← Home

@syncfusion/ej2-vue-filemanager

npm Repository Homepage

Essential JS 2 FileManager Component for Vue

12
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

syncfusionorgessentialjs2syncfusion-javascript

Keywords

vuevuejsvue-filemanagervue-file organizervue-file organizing toolvue-file pickervue-file viewervue-file browservue-file selectorvue-directory viewer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): syncfusion-javascript is the new org publisher account with 182 approved packages; consistent org-wide migration from essentialjs2. ai
license uncommon-license:SEE LICENSE IN license AI (license): Syncfusion's standard commercial license format; stable across all their packages. ai
provenance no-provenance AI (provenance): Syncfusion does not publish with Sigstore provenance; consistent across their package ecosystem. ai

Versions (showing 12 of 12)

Version Deps Published
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

v33.2.10

1 finding
INFO No provenance attestation provenance

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

v33.2.6

1 finding
INFO No provenance attestation provenance

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

v33.2.3

1 finding
INFO No provenance attestation provenance

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

v33.1.47

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.

v33.1.45

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.

v33.1.44

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.

v32.2.7

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.

v32.2.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v32.1.19

2 findings
HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2025-12-16) provenance

This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

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.