@syncfusion/ej2-vue-navigations SEE LICENSE IN license 21 versions

@syncfusion/ej2-vue-navigations

npm Repository Homepage

A package of Essential JS 2 navigation components such as Tree-view, Tab, Toolbar, Context-menu, and Accordion which is used to navigate from one page to another for Vue

21

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

vueej2-vue-navigations vue-navigationsvue-toolbar vue-tabvue-routing vue-contextmenuvue treevue treeviewvue tree componentvue menuvue menu componentvue breadcrumbvue carouselvue appbarvue stepper

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
license	uncommon-license:SEE LICENSE IN license	AI (license): Syncfusion uses a custom commercial license; stable pattern across all their packages.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Syncfusion packages consistently have large README link dumps pointing to their component docs; not spam or phishing.	ai	2026/05/14

Versions (showing 21 of 21)

Version	Deps	Published
33.2.10	3 / 0	2026-06-02
33.2.8	3 / 0	2026-05-26
33.2.7	3 / 0	2026-05-19
33.2.6	3 / 0	2026-05-12
33.2.4	3 / 0	2026-04-28
33.2.3	3 / 0	2026-04-21
33.1.49	3 / 0	2026-04-14
33.1.47	3 / 0	2026-04-07
33.1.46	3 / 0	2026-03-31
33.1.45	3 / 0	2026-03-24
33.1.44	3 / 0	2026-03-16
32.2.9	3 / 0	2026-03-10
32.2.8	3 / 0	2026-03-03
32.2.7	3 / 0	2026-02-24
32.2.6	3 / 0	2026-02-24
32.2.3	3 / 0	2026-02-05
32.1.24	3 / 0	2026-01-20
32.1.19	3 / 0	2025-12-16
31.2.16	3 / 0	2025-12-02
31.2.12	3 / 0	2025-11-18
31.2.5	3 / 0	2025-11-04

v33.2.10

1 finding

LOW No provenance attestation provenance

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

v33.2.8

1 finding

LOW No provenance attestation provenance

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

v33.2.7

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v32.2.6

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: syncfusion-javascript.

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

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.

v31.2.5

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.