Tests, release notes, and a five-person contributor spread add useful confidence. The repository remains active, but no security policy and partly unpinned workflow actions leave maintenance hygiene below ideal.
78%
Total Score
100
88
75
Only two releases have appeared since June 2022, with the latest registry release in April 2023 and none in the last 12 months. Recent repository activity partly offsets the stale registry cadence, but release transparency remains a concern.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy file. That weakens vulnerability-reporting transparency, although the active organization-backed repository provides some compensating maintenance capacity.
The single workflow was fully analyzed with no injection or high-severity findings, but two of four action references are unpinned. The workflow has no top-level permissions block, which is acceptable on its own.
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.0.0 || ^4.0.0 | — | — |
spryker/product Version ^6.0.0 | — | — |
spryker/discount Version ^9.0.0 | — | — |
spryker/transfer Version ^3.25.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.