Usable with caveats: the package is clearly licensed, tested, lightweight, and backed by a matching organization repository, but its registry release history has been inactive for more than three years and recent repository activity is absent. Review ongoing project support before adopting it for a critical payment flow.
65%
Total Score
75
100
88
75
The package has only three releases and no releases in the last 12 months; its latest registry release was over three years ago, which is a meaningful maintenance concern despite the package not being deprecated.
There were no commits and no active maintainers in the last three months, weakening evidence of ongoing maintenance; the January 2025 push partially offsets but does not remove this concern.
The repository uses Make and Composer build tooling, but it has no detected security-scanning tools, leaving a modest transparency and assurance gap.
No security policy was found in the repository, reducing clarity about vulnerability reporting and maintenance expectations for a payment-related component.
The only workflow lacks top-level token permissions. No write permissions were detected, but explicitly restricting workflow permissions would provide stronger supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/payment-extension 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.