← Home

@syncfusion/ej2-angular-filemanager

npm Repository Homepage

Essential JS 2 FileManager Component for Angular

11
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

angularangular-filemanagerangular-file organizerangular-file organizing toolangular-file pickerangular-file viewerangular-file browserangular-file selectorangular-directory viewer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Syncfusion releases in batches across many packages; dormancy between major release cycles is expected for this org. ai
dependencies unvetted-dep:@syncfusion/ej2-filemanager AI (dependencies): Same-org Syncfusion dependency; expected peer for this Angular wrapper package across all versions. ai
phantom-deps phantom-dep:@syncfusion/ej2-base AI (phantom-deps): Same-org transitive dep; declared but re-exported indirectly — stable false positive for this package family. ai

Versions (showing 11 of 11)

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

1 finding
LOW No provenance attestation provenance

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

v33.2.3

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

v32.2.3

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.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

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.