The package is clearly licensed, documented, tested, and has no install-time scripts. Repository security coverage is thinner than its maintenance evidence, with no security policy or scanning tool and two of four workflow actions unpinned.
84%
Total Score
100
94
67
The project uses Composer, but no security-scanning tools were detected. That leaves a modest gap in automated security hygiene despite the active build tooling.
No repository security policy was found. This weakens vulnerability-reporting transparency, although it is outweighed by the repository's recent activity and organizational backing.
All workflows were analyzed with no audit findings, dangerous triggers, untrusted checkouts, or script injections. However, two of four action references are unpinned, a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.0.0 || ^4.6.0 || ^5.0.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.