The package is well documented and tested, with recent changes spread across six contributors. Its repository lacks a security policy and automated security scanning, while two of four workflow actions are unpinned.
86%
Total Score
100
94
75
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
No repository security policy was found, which makes vulnerability reporting and response expectations less clear.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injections, or audit findings; two of four action references are unpinned, a minor reproducibility concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/user Version ^3.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.20.0 | — | — |
spryker/customer Version ^7.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.