spryker/navigation-gui
Healthy and suitable to depend on. It has a long release history, regular recent releases, active multi-contributor maintenance, complete package documentation and tests, and an unarchived repository; the main gaps are the missing security policy and undeclared workflow token permissions.
90%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no repository security-scanning tools were detected, leaving a modest security-process transparency gap.
No SECURITY.md or other security policy was found, so the project does not document a vulnerability-reporting process.
The CI workflow does not declare top-level token permissions. No write permissions or dangerous workflow patterns were observed, but least-privilege intent is not explicit.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/cms Version ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 | — | — |
spryker/gui Version ^4.0.0 || ^5.6.0 | — | — |
spryker/url Version ^3.5.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 days ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.