The organization-backed repository includes a README, changelog, and release notes for this version. Security scanning is absent, and development has slowed substantially, so pinning this release carries maintenance risk.
58%
Total Score
75
70
50
The package has had no registry release for over four years, with zero releases in the last 12 months. Its five-release history shows a real maintenance gap for a payment integration.
The repository recorded zero commits and zero active maintainers in the last three months. This indicates currently inactive development, although the repository was pushed more recently than the registry release history.
Composer build tooling is present, but the repository reports no security scanning tools. That is a transparency and maintenance weakness for payment-processing code.
The repository has no security policy. This reduces transparency for reporting and handling issues, though it does not by itself show abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/oms Version ^7.0.0 || ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/quote Version ^2.0.0 | — | — |
spryker/sales Version ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/refund Version ^5.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.