Clear release notes and a licensed artifact support dependable use. The workflow has two unpinned actions, and no security policy or automated security scanning is present.
88%
Total Score
100
93
50
Composer build tooling is present, but no automated security-scanning tool was detected, leaving a modest assurance gap despite the active repository.
The repository has no published security policy, which leaves vulnerability-reporting expectations less transparent; this is a modest documentation gap, not evidence of unsafe code.
The single workflow was fully analyzed with no injection, untrusted-checkout, or severity findings. Two of four action references are unpinned, a minor reproducibility concern, while the absence of a top-level permissions block is acceptable on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/customer Version ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 | — | — |
spryker-shop/shop-ui Version ^1.54.0 || ^2.0.0 | — | — |
spryker/business-on-behalf Version ^1.1.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.