Clear documentation and a focused dependency set make adoption straightforward. The repository lacks a security policy and leaves half of its workflow references unpinned, so maintenance hygiene is not perfect.
84%
Total Score
100
100
94
75
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest repository hygiene gap.
The repository has no documented security policy, reducing transparency about vulnerability reporting and response expectations.
The single workflow was fully analyzed with no audit findings or untrusted execution paths. However, two of four action references are unpinned, which weakens build reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^4.0.0 || ^5.8.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/product-offer-gui-extension Version ^1.0.0 | — | — |
spryker/product-offer-service-point Version ^1.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.