Navigation [feature]
70%
Total Score
67
94
50
All 3 recent commits came from one contributor, spryker-release-bot, giving that contributor a 100% share. Organization backing reduces handoff risk, but the observed recent activity is still highly concentrated.
The repository recorded 3 commits in the last 3 months, showing some recent activity. The activity is limited, so it provides only moderate maintenance evidence.
Composer build tooling is present, but no security scanning tools were detected. This leaves a meaningful supply-chain hygiene gap for an actively published package.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it is not evidence that the package is unsafe by itself.
The single workflow was fully analyzed with no injection or high-severity findings, but all 4 action references are unpinned. Unpinned actions weaken build reproducibility and update control.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/navigation Version ^2.10.0 | — | — |
spryker/navigation-gui Version ^3.2.0 | — | — |
spryker/content-navigation Version ^1.0.0 | — | — |
spryker/navigation-storage Version ^1.14.0 | — | — |
spryker/content-navigation-gui Version ^1.2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.