It includes tests, a changelog, release notes, and a repository that clearly matches the package. Workflow checks found no dangerous findings, although the project reports no security policy or automated security-scanning tool.
88%
Total Score
100
100
94
83
Composer build tooling is present, but no security-scanning tool was detected; this is a modest transparency and maintenance gap, not evidence of abandonment.
The repository has no security policy, leaving disclosure and response expectations undocumented; the active organization and repository activity partly offset this gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/twig Version ^3.0.0 | — | — |
spryker/event Version ^1.0.0 || ^2.0.0 | — | — |
spryker/touch Version ^3.1.0 || ^4.0.0 | — | — |
spryker/kernel Version ^3.52.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.