@syncfusion/ej2-angular-navigations
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 Angular
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely a CI/CD pipeline change during org account migration; no other malicious signals present. | ai | |
| provenance | publisher-changed | AI (provenance): Syncfusion org-wide account migration from essentialjs2 to syncfusion-javascript; consistent across all their packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Syncfusion packages consistently have link-heavy READMEs; not indicative of spam or phishing for this org. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-base | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a stable false positive for Syncfusion's modular package structure. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 33.2.8 | 3 / 0 | |
| 33.2.7 | 3 / 0 | |
| 33.2.6 | 3 / 0 | |
| 33.2.4 | 3 / 0 | |
| 33.2.3 | 3 / 0 | |
| 33.1.49 | 3 / 0 | |
| 33.1.47 | 3 / 0 | |
| 33.1.46 | 3 / 0 | |
| 33.1.45 | 3 / 0 | |
| 33.1.44 | 3 / 0 | |
| 32.2.9 | 3 / 0 | |
| 32.2.8 | 3 / 0 | |
| 32.2.7 | 3 / 0 | |
| 32.2.6 | 3 / 0 | |
| 32.2.3 | 3 / 0 | |
| 32.1.24 | 3 / 0 | |
| 32.1.19 | 3 / 0 | |
| 31.2.16 | 3 / 0 | |
| 31.2.12 | 3 / 0 | |
| 31.2.5 | 3 / 0 |
v33.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.2.6
3 findingsThis 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.
This version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.24
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.1.19
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v31.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.