Healthy and suitable to depend on. It has a long release history, a current stable release, recent commits from five contributors, and clear organization backing; the main caveats are the absence of a security policy and undeclared workflow token permissions.
86%
Total Score
100
100
94
80
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency gap, not a severe risk, because other repository and workflow signals are available.
The repository has no security policy, leaving vulnerability-reporting expectations and response procedures undocumented. Organization backing and active maintenance partly reduce the concern but do not remove this documentation gap.
The only workflow lacks top-level token permissions, so its GitHub Actions permissions are not explicitly constrained. No write permissions were observed, limiting the severity, but least-privilege intent is not documented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.45.0 || ^4.0.0 || ^5.6.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.1.0 || ^4.0.0 | — | — |
spryker/product Version ^5.0.0 || ^6.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.