The repository has no security policy or security-scanning tools, and two of four workflow actions are unpinned. Tests, release notes, recent commits, and five active contributors provide useful transparency.
82%
Total Score
100
93
50
The repository uses Composer build tooling, but no security-scanning tools were detected. That is a maintenance and supply-chain hygiene gap, though it is not evidence of an unsafe release by itself.
No repository security policy was found. This weakens vulnerability-reporting transparency for a package that provides infrastructure integration.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, two of four action references are unpinned, leaving a moderate reproducibility and action-integrity gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/redis Version ^2.13.0 | — | — |
spryker/kernel Version ^3.72.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.8.0 | — | — |
spryker/storage-extension Version ^1.1.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.