snowdog / module-hyva-checkout-santander

snowdog/module-hyva-checkout-santander

Hyva Checkout compatybility module for Santander eRaty

magento2-module Compatibility: Not yet tested Code Quality: Fail Tests: N/A Security: Pass

Hyvä Checkout Santander

Hyvä Magewire Checkout compatibility module for aurora/module-santander

Hyvä Checkout

Hyvä Magewire Checkout is flexible and highly configurable checkout replacement for Magento 2.
See more at hyva.io

Santander eRaty Credit Payment

This module extends original Magento2 module for Santander eRaty to be able to use it within Hyvä Magewire Checkout.
See original module at eRaty download page

Changelog

[Unreleased]

[1.4.0] - 2025-07-07

  • Hyva checkout 1.3.0 compatibility

[1.3.0] - 2024-12-16

  • Add frontend validation

[1.1.0] - 2023-10-27

  • DEV-103096 - TOS Checkbox

[1.0.0] - 2023-10-13

  • Initial release
Versions
Version Stability QA Status Compatibility Released
1.4.0 stable Pass Not yet tested Details 2025-07-07 11:12:45
1.3.0 stable Not tested Not yet tested Details 2025-01-03 12:50:08
1.2.0 stable Not tested Not yet tested Details 2024-12-02 07:52:49
1.1.0 stable Not tested Not yet tested Details 2023-10-27 11:18:15
1.0.0 stable Not tested Not yet tested Details 2023-10-13 15:49:53

Requires 1

Package Constraint
aurora/module-santander *

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 not tested not tested
2.4.8 not tested not tested
2.4.9 not tested not tested

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 4 4 warnings (ruleset: Magento2) — 1 auto-fixable with phpcbf
PHPMD Warning 2 2 rule violations (UnusedFormalParameter:2)
Cpd Pass 0
Composer validate Info 2 valid; 2 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Error Error
2.4.8 Error Error
2.4.9 Error Error

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit N/A 0 no resolvable dependency tree to audit — Your requirements could not be resolved to an installable set of packages. Problem 1
Malware scan Pass 0

No license declared

This package's composer.json doesn't declare a license, homepage, or authors. Check the source repository for terms of use.

More from snowdog

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.