The stable major release, MIT licensing, automated tests, and organization-backed repository provide useful support. Its long publishing gap and absent recent commits make ongoing maintenance uncertain; pin this version only if that trade-off fits.
60%
Total Score
83
100
88
75
The package has six releases, but none in the last 12 months and its latest release was over three years ago. This creates a meaningful maintenance concern despite its established release history.
There were no commits and no active maintainers in the last three months. Combined with the old latest registry release, this is evidence of reduced current maintenance.
The repository uses Make and Composer, but no security-scanning tool was detected. This is a hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy. That weakens the project's documented process for handling vulnerabilities, although it does not by itself show abandonment.
The single workflow was fully analyzed with no injection or high-severity findings, but all three action references are unpinned. The absence of a top-level permissions block is acceptable on its own; unpinned actions remain a modest reproducibility and update risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/cart Version ^5.0.0 || ^6.0.0 || ^7.0.0 | — | — |
spryker/quote Version ^2.0.0 | — | — |
spryker/zed-request Version ^3.3.0 | — | — |
spryker/glossary-storage Version ^1.0.0 | — | — |
spryker/glue-application 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.