Healthy and suitable to use. It has current releases, active organizational maintenance, broad contributor activity, and complete package and repository structure; the main caveat is limited security-process documentation and scanning.
88%
Total Score
100
100
94
80
The repository uses Composer build tooling, but no security-scanning tool was detected. The missing scan is a process gap, though it is not evidence of abandonment.
The repository has no security policy. This weakens vulnerability-reporting transparency, but active releases and organizational ownership partly compensate for the gap.
The one CI workflow does not declare top-level token permissions. No write permissions were detected, but explicit least-privilege settings would provide stronger CI hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/url Version ^3.3.0 | — | — |
spryker/store Version ^1.9.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.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.