vaimo / kustom-module-siwk
vaimo/kustom-module-siwk
Sign in with Kustom Magento 2 Extension
No README yet
The vendor hasn't published a README for this package. The latest version's install command is on the right.
1.0.15 / 2026-03-06
- KUSTOM-63 Compatibility with PKSA-y2cr-5h3j-g3ys Security Advisory
1.0.13 / 2025-06-03
- PPP-2071 Fixed callback url
1.0.12 / 2025-05-21
- PPP-2055 Compatibility with AC 2.4.8 and PHP 8.4
1.0.11 / 2025-04-23
- PPP-1814 Added Interoperability functionality
1.0.10 / 2025-04-03
- PPP-1832 Fixed locale
- PPP-1860 Simplified repository classes for database abstractions
1.0.9 / 2025-03-27
- PPP-2026 Increased version because of new dependencies
1.0.8 / 2025-02-11
- PPP-1983 Increased version because of new dependencies
1.0.7 / 2025-01-22
- PPP-1760 Added API test for Klarna\Siwk\Model\Authentication\Api\Endpoints\Jwks
- PPP-1761 Added API test for \Klarna\Siwk\Model\Authentication\Api\Endpoints\OpenIdConfiguration
- PPP-1859 Simplified unit tests by using a helper which includes the mocking logic.
1.0.6 / 2024-12-03
- PPP-1913 Setting the DOB to the customer account if the DOB exists
1.0.5 / 2024-11-05
- PPP-1784 Fix conflicting loads of Klarna web SDKs
- PPP-1830 List required and default activated scopes for Sign in with Klarna
1.0.4 / 2024-10-18
- PPP-1714 Simplify composer.json files
- PPP-1726 SIWK - update scope from payment:request:create to customer:login
1.0.3 / 2024-09-26
- PPP-1521 Using the store instance to fetch the locale
1.0.2 / 2024-08-30
- PPP-1665 Changed in the database table klarna_siwk_customer the type of the column klarna_customer_id from text to varchar so that it can be indexed
- PPP-1671 Checking if the access token is an empty string
1.0.1 / 2024-08-21
- PPP-1652 Updated the version because of new version dependencies
1.0.0 / 2024-08-12
- PPP-754 Added Sign-in with Klarna
Requires 4
| Package | Constraint |
|---|---|
| firebase/php-jwt | ^6.9.0||^7.0 |
| vaimo/kustom-module-base | 11.0.* |
| magento/framework | ^103 |
| php | ~7.4.0||~8.1.0||~8.2.0||~8.3.0||~8.4.0 |
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.
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.
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.
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
| 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
| 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.
More from Vaimo
View vendorTurn 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.