Healthy and suitable to depend on. It has regular releases, active contributions from five maintainers, clear repository backing, tests, and a stable package structure; the main gaps are the lack of a security policy and repository security scanning.
88%
Total Score
100
93
75
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The single workflow has no top-level token permissions declaration. Although no dangerous workflow patterns or write permissions were observed, explicit least-privilege settings would improve repository hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^4.0.0 || ^5.6.0 | — | — |
spryker/store Version ^1.9.0 | — | — |
spryker/kernel Version ^3.33.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/product Version ^6.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.