Healthy and suitable to use, with some maintenance and security-hygiene caveats. It has a long release history, a current stable release, active organizational backing, and a matching repository, but recent commits come only from one release bot and the repository lacks a security policy and explicit workflow permissions.
78%
Total Score
63
94
75
All 3 recent commits came from one contributor, spryker-release-bot. Organizational backing reduces the risk of a permanently unavailable individual maintainer, but no second active contributor is visible in this period.
The repository received 3 commits in the last 3 months, showing recent activity but a relatively light maintenance pace.
There were no new or merged pull requests in the last month and no new issues, so recent collaboration activity is limited, although this does not by itself show abandonment.
Composer is used for builds, but no security-scanning tools were detected, leaving a security-hygiene gap in the repository.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/category Version ^5.24.0 | — | — |
spryker/category-gui Version ^2.8.0 | — | — |
spryker/category-image Version ^1.5.0 | — | — |
spryker/category-storage Version ^2.12.0 | — | — |
spryker/category-exporter Version ^3.0.2 | — | — |
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.