← Home

@syncfusion/ej2-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

25
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

ej2syncfusionweb-componentsjavascripttypescriptmodeltoolbarhorizontal-scrollribbonnavbarnavigation-bartoolbar-customizationscrollable-toolbartoolbar-popupmultirow-toolbarextended-toolbaroverflowcommand-buttonsaccordionpanelbarejTabtabtabStripscrollable-tabpopup-tabmultirow-tabheader-orientationclose-tabtab-wizardtab-with-menuejAccordionaccordionaccordion-wizardmultiple-open-panel-barmultiple-open-accordionpanel-barcollapsible-panel-barcontext-menucontext menucontextmenuej2 contextmenutreeviewtreeej2-treeviewtree structurehierarchical structuretree navigationtreeview-checkboxdrag and droptree editingload on demandaccordion treesidebardock sizeshowbackdroptargetpositiondockgesturessticky-sidebarfixedhamburgersidenavnavhamburger-menuside-menunavigation-barstickydrawerslidebarslideslide-panelmultiple-sidebarslide-navigationnavigation-drawerbreadcrumbbreadcrumb navigationbreadcrumb trailej2 breadcrumbnavigation linksnavigational aidprevious page navigationcurrent page hierarchycurrent page locationpath of urltrace page locationlist of breadcrumb links

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publish-env metadata change on established first-party package; no behavioral risk. ai
dependencies unvetted-dep:@syncfusion/ej2-data AI (dependencies): Sibling Syncfusion package at matching version; expected monorepo dependency pattern. ai
dependencies unvetted-dep:@syncfusion/ej2-lists AI (dependencies): Sibling Syncfusion package at matching version; expected monorepo dependency pattern. ai
dependencies unvetted-dep:@syncfusion/ej2-inputs AI (dependencies): Sibling Syncfusion package at matching version; expected monorepo dependency pattern. ai
dependencies unvetted-dep:@syncfusion/ej2-base AI (dependencies): Sibling Syncfusion package at matching version; expected monorepo dependency pattern. ai
dependencies unvetted-dep:@syncfusion/ej2-buttons AI (dependencies): Sibling Syncfusion package at matching version; expected monorepo dependency pattern. ai
bogus-package bogus-package AI (bogus-package): Syncfusion's marketing-heavy READMEs with many links are a known pattern across their entire component suite, not phishing. ai
dependencies unvetted-dep:@syncfusion/ej2-popups AI (dependencies): Sibling Syncfusion package at matching version; expected monorepo dependency pattern. ai

Versions (showing 25 of 25)

Version Deps Published
34.1.31 6 / 0
34.1.30 6 / 0
34.1.29 6 / 0
33.2.15 6 / 0
33.2.10 6 / 0
33.2.8 6 / 0
33.2.7 6 / 0
33.2.6 6 / 0
33.2.4 6 / 0
33.2.3 6 / 0
33.1.49 6 / 0
33.1.47 6 / 0
33.1.46 6 / 0
33.1.45 6 / 0
33.1.44 6 / 0
32.2.9 6 / 0
32.2.8 6 / 0
32.2.7 6 / 0
32.2.6 6 / 0
32.2.3 6 / 0
32.1.24 6 / 0
32.1.19 6 / 0
31.2.16 6 / 0
31.2.12 6 / 0
31.2.5 6 / 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.30

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

1 finding
LOW No provenance attestation provenance

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

v32.2.8

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-01-20, known maintainer) provenance

This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-01-20, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v32.1.19

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: essentialjs2 → syncfusion-javascript (on 2025-12-16, known maintainer) provenance

This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2025-12-16, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v31.2.16

1 finding
LOW No provenance attestation provenance

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.

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.