Documentation, tests, and release notes make integration easier. Workflow auditing found no dangerous patterns, while the missing security policy and security scanning leave some process visibility gaps.
85%
Total Score
100
94
50
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning layer is a modest process-visibility gap rather than evidence of unsafe code.
No repository security policy was detected. This limits documented vulnerability-reporting guidance, though the active organization-backed repository provides some compensating maintenance context.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/store Version ^1.19.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/country Version ^3.2.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.