Documentation, tests, and release notes make integration easier. The missing security policy and two unpinned workflow actions are minor transparency and build-hygiene gaps.
84%
Total Score
100
100
94
83
Composer build tooling is present, but no security scanning tools were detected. That is a modest security-process gap, not evidence of unsafe code by itself.
No repository security policy was found, reducing transparency about vulnerability reporting and response procedures.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, which is 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/kernel Version ^3.30.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/propel-orm Version ^1.0.0 | — | — |
spryker/product-offer Version ^1.10.0 | — | — |
spryker/shipment-type 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.