mage-os / mageos-common-async-events

mage-os/mageos-common-async-events

Send REST requests to external endpoints asynchronously. This module implements the most common events like order creation and customer change.

magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Fail Tests: N/A Security: Pass MIT

Mage-OS Common Asynchronous Events

Send REST requests to external endpoints asynchronously. This module implements the most common events like order creation and customer change.

This module uses the Mage-OS Asynchronous Events module as a basis.

Installation

composer require mage-os/mageos-common-async-events

If you run into an error like "Could not find a version of package mage-os/mageos-common-async-events matching your minimum-stability (stable).", run this command instead:

composer require mage-os/mageos-common-async-events @dev

Enable and install the module:

bin/magento setup:upgrade

Usage

You can now use the following events without having to implement them yourself.

Event identifier Description Remarks
customer.created Whenever a customer is created
customer.updated Whenever a customer is saved, except it's new
customer.login Whenever a customer logs in successfully
customer.address.created Whenever a customer address is created
customer.address.updated Whenever a customer address is saved, except it's new
sales.order.created When a new order is created
sales.order.updated When the state of an existing order is changed
sales.order.paid When an order is fully paid
sales.order.shipped When an order is fully shipped
sales.order.holded When an order is set "on hold"
sales.order.unholded When an order is released from "on hold"
sales.order.cancelled When an order is cancelled
sales.shipment.created When a new shipment is created
sales.invoice.created When a new invoice is created
sales.invoice.paid When an invoice is paid
sales.creditmemo.created When a new creditmemo is created
catalog.product.created When a new product is created
catalog.product.updated When a product is updated
cms.page.created When a CMS page has been created
cms.page.updated When a CMS page is updated
cms.block.created When a CMS block has been created
cms.block.updated When a CMS block is updated

You can use these events by

3rd Party Events

Event identifier Description Module
customer.login_failed Whenever a customer fails to log in zero1/async-event-customer-login-failed
customer.create_failed Whenever a customer fails to sign up for an account zero1/async-event-customer-create-failed

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
0.6.1 stable Fail Magento 2.4.7-2.4.9 Details 2026-03-04 07:59:10
0.6.0 stable Not tested Not yet tested Details 2026-02-25 09:10:03
0.5.2 stable Not tested Not yet tested Details 2025-12-23 09:02:01
0.5.1 stable Not tested Not yet tested Details 2025-04-12 07:33:40
0.5.0 stable Not tested Not yet tested Details 2025-02-06 07:12:51
0.4.3 stable Not tested Not yet tested Details 2024-12-09 15:04:00
0.4.2 stable Not tested Not yet tested Details 2024-12-09 10:41:24
0.4.1 stable Not tested Not yet tested Details 2024-11-29 09:15:49
0.4.0 stable Not tested Not yet tested Details 2024-11-21 15:29:03
0.3.2 stable Not tested Not yet tested Details 2024-09-18 07:23:08
0.3.1 stable Not tested Not yet tested Details 2024-09-18 06:42:11
0.3.0 stable Not tested Not yet tested Details 2024-09-16 07:10:22
0.2.1 stable Not tested Not yet tested Details 2024-07-15 09:01:03
0.2.0 stable Not tested Not yet tested Details 2023-11-22 10:01:50
0.1.0 stable Not tested Not yet tested Details 2023-09-08 11:49:16

Requires 3

Package Constraint
php >=8.1
magento/framework *
mage-os/mageos-async-events *

Requires-dev 2

Package Constraint
squizlabs/php_codesniffer ~3.5
magento/magento-coding-standard *

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 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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 8 8 warnings (ruleset: Magento2) — 3 auto-fixable with phpcbf
PHPMD Pass 0
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 25 25
2.4.8 25 25
2.4.9 25 25

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 Pass 0
Malware scan Pass 0
License
MIT

More from mage-os

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.