The repository is still unarchived and matches the package, with tests and release notes. Organization backing helps, but no recent commits and no security policy leave little evidence of ongoing support.
20%
Total Score
75
67
50
Packagist marks the entire package as abandoned, with no replacement specified. This is a severe adoption risk even though the linked repository remains active and organization-owned.
The latest registry release was in July 2020, with no releases in the last 12 months. The historical cadence was regular, but the prolonged release gap indicates abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months. This weakens evidence of ongoing maintenance, despite a more recent repository push being recorded elsewhere.
The repository has no security policy, leaving vulnerability-reporting and response expectations unclear. This is a transparency gap for a package with substantial runtime dependencies.
The single analyzed workflow has no audit findings and no untrusted triggers or sinks, but all four action references are unpinned. That is a supply-chain hygiene gap, not a severe risk by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/cart Version ^5.0.0 || ^7.0.0 | — | — |
spryker/user Version ^3.0.0 | — | — |
spryker/sales Version ^8.10.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/propel 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.