Healthy and suitable to depend on. It has a long release history, a recent stable release cadence, active contributors, and a complete package with tests and documentation. Repository security-policy and workflow-permission hygiene could be stronger.
88%
Total Score
100
100
94
80
The repository uses Composer build tooling, but no security-scanning tool was detected. This is a modest transparency gap, not a severe concern given the active project and other safeguards.
No repository security policy was found. This weakens the documented vulnerability-reporting path, although it is not evidence that the package is unsafe or abandoned.
The repository's one workflow does not declare top-level token permissions. No write permissions were detected, but explicit least-privilege declarations would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.48.0 || ^4.3.3 || ^5.5.0 | — | — |
spryker/twig Version ^3.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/symfony Version ^3.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.