Healthy and suitable to use. It has a current stable release, recent activity from six contributors, organizational backing, and a matching source repository; the main caveats are missing security-policy and explicit workflow permissions, plus no automated security scanning.
84%
Total Score
88
100
89
80
There were no new or closed issues or pull requests in the last month, and the number of open issues is unknown. This is a limited maintenance signal, though recent commits provide stronger evidence of activity.
The repository has no stars or forks and only three watchers, which offers little external adoption evidence. Popularity is supporting evidence, so this is a modest concern rather than a health verdict.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning capability is a transparency and maintenance gap, not evidence of maliciousness.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is partly offset by the active organization-backed repository.
The only workflow lacks top-level token permissions, so its GitHub Actions permission boundary is not explicitly documented. No top-level write permissions were detected.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.52.0 | — | — |
spryker/symfony Version ^3.1.0 | — | — |
spryker-shop/shop-ui Version ^1.0.0 || ^2.0.0 | — | — |
spryker/product-set-page-search Version ^1.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.