Tests, changelog, balanced contributors, and no install scripts reduce operational risk. Unpinned workflow actions and no security policy leave modest process gaps.
84%
Total Score
100
88
75
The package has existed since 2020 and released as recently as May 2026, but only one release appeared in the last 12 months and releases are spaced about 195 days apart.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest verification gap.
The repository has no security policy, which makes vulnerability reporting and disclosure expectations less transparent for adopters.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, two of four action references are unpinned, reducing reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.5.0 || ^4.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/event-behavior Version ^1.17.0 | — | — |
spryker/product-storage Version ^1.26.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.