Healthy and suitable to use. It has a long release history, recent releases, active contributions from five maintainers, and complete package documentation and tests; the main gaps are the absent security policy and security scanning.
88%
Total Score
100
100
94
80
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and vulnerability-management gap, though it is not evidence of abandonment.
The repository has no security policy. That weakens disclosure transparency for a dependency, although active maintenance and organization backing provide some compensation.
The one workflow does not declare top-level token permissions, so its required access is less explicit than preferred. It does not declare top-level write access, limiting the concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/cache Version ^3.1.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/propel Version ^3.0.0 | — | — |
spryker/search Version ^6.0.0 || ^7.0.0 || ^8.0.0 | — | — |
spryker/symfony Version ^3.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.