The package includes clear documentation and release notes for integration, while its workflow audit found no dangerous findings. The absent security policy and two unpinned actions are minor transparency and build-hygiene drawbacks.
86%
Total Score
100
94
75
Composer build tooling is present, but no security-scanning tools were detected. This is a modest repository-hygiene gap, not evidence of unsafe code by itself.
The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting expectations unclear.
All workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, two of four action references are unpinned, which is a minor build reproducibility and supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/propel Version ^3.47.0 | — | — |
spryker/product Version ^5.5.0 || ^6.0.0 | — | — |
spryker/storage Version ^3.4.0 | — | — |
spryker/transfer Version ^3.27.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.