The repository lacks a security policy, and two of four workflow actions are not pinned. Tests, release notes, and organization backing provide useful transparency.
88%
Total Score
100
93
50
Composer build tooling is present, but no security scanning tools were detected. This is a modest security-process gap, not evidence of unsafe code.
No repository security policy was found, reducing the transparency of vulnerability reporting and response expectations.
The single workflow was fully analyzed with no audit findings, no untrusted checkouts, and no script injection; however, two of four action references are unpinned, leaving a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^2.0.0 || ^3.0.0 | — | — |
spryker/url Version ^3.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/router Version ^1.12.0 | — | — |
spryker/laminas 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.