Healthy and suitable to use, with strong recent release and contributor activity from an organization-backed project. The main caveat is limited security-process transparency: no security policy or repository security scanning was found, and the CI workflow does not declare top-level token permissions.
83%
Total Score
100
100
94
80
Composer build tooling is present, but no security-scanning tool was detected. This leaves a modest gap in repository security hygiene.
No repository security policy was found, reducing transparency about vulnerability reporting and response procedures.
The CI workflow does not declare top-level token permissions. Although no write-enabled top-level permissions were observed, explicit least-privilege settings would provide stronger security assurance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.54.0 || ^4.0.0 || ^5.6.0 | — | — |
spryker/store Version ^1.15.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/symfony Version ^3.0.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.