Healthy and suitable to use, with minor transparency and CI-hygiene caveats. It has regular releases, six active contributors, tests, a matching repository, and no deprecation or archive status; the main gaps are no security policy and unspecified workflow token permissions.
84%
Total Score
100
50
94
80
The package declares 15 runtime dependencies, including several Spryker and Symfony integrations. This is a meaningful dependency surface that increases upgrade and compatibility work, but it is consistent with a framework integration module rather than an unexplained excess.
The repository uses Composer build tooling, but no security-scanning tool was detected. The missing scanner is a transparency gap, though it is not evidence of unsafe code by itself.
No repository security policy was found. That weakens the project's documented process for reporting and handling vulnerabilities, though active releases and a backed repository provide some compensation.
The only workflow does not declare top-level token permissions. No write permissions were observed, but the lack of an explicit restriction leaves CI access less transparent than it should be.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^5.0.0 | — | — |
spryker/log Version ^3.20.0 | — | — |
spryker/lock Version ^1.1.0 | — | — |
spryker/redis Version ^2.13.0 | — | — |
spryker/kernel Version ^3.30.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.