It has a clear consumer README, a licensed artifact, and no install-time scripts. The remaining concerns are limited to absent security-policy and security-scanning signals and two unpinned workflow actions.
84%
Total Score
100
94
75
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and hygiene gap, not evidence of unsafe code.
No repository security policy was found. That weakens vulnerability-reporting transparency, although active maintenance and testing provide some compensation.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, two of four action references are unpinned, leaving a limited reproducibility and action-integrity gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.33.0 | — | — |
spryker/product Version ^5.7.0 || ^6.11.0 | — | — |
spryker/category Version ^3.0.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/messenger 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.