Clear documentation, tests, release notes, and a matching source tree support routine integration. The repository has no security policy and two of four workflow actions are unpinned, but neither indicates an immediate dependency concern.
88%
Total Score
100
94
88
Composer build tooling is present, but no security scanning tools were detected. That limits automated security hygiene evidence without indicating abandonment.
The repository has no published security policy. This is a transparency gap, although the available maintenance and release evidence provides compensating project maturity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/user Version ^3.7.0 | — | — |
spryker/store Version ^1.19.0 | — | — |
spryker/kernel Version ^3.72.0 | — | — |
spryker/propel Version ^3.8.0 | — | — |
spryker/product Version ^6.9.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.