Healthy and suitable to use, with minor transparency and workflow caveats. It has a current stable release, active contributors, tests, changelog, and organizational backing; the repository lacks a security policy and explicit workflow token permissions.
84%
Total Score
100
100
94
80
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency gap rather than a decisive health problem because the repository otherwise has CI and active maintenance.
No repository security policy was found. That weakens vulnerability-reporting transparency, although it is partly offset by the repository's active maintenance and organization ownership.
The only workflow lacks top-level token permissions. No write permissions were declared, so this is a least-privilege documentation gap rather than evidence of dangerous access.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/store Version ^1.19.0 | — | — |
spryker/config Version ^3.0.0 | — | — |
spryker/kernel Version ^3.64.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.25.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.