Healthy and suitable to depend on. It has a long, steady release history, active organization-backed maintenance, broad tests and documentation, and no deprecation or archive warning; repository security-policy and workflow-permission hygiene are the main gaps.
90%
Total Score
100
100
94
80
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a transparency and hygiene gap, not evidence that the package is unsafe or unmaintained.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear, creating a modest transparency gap despite the otherwise active project.
The CI workflow declares no top-level token permissions. Although no write permissions were detected, explicit least-privilege permissions would provide better workflow hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.7.0 | — | — |
spryker/event Version ^1.0.0 || ^2.0.0 | — | — |
spryker/price Version ^5.0.0 | — | — |
spryker/quote Version ^2.1.0 | — | — |
spryker/store Version ^1.12.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.