catgento / module-admin-activity
catgento/module-admin-activity
The Admin Activity extension makes it easy to track all admin activity and revert the modification.
This module was initially developed by by KiwiCommerce. The original repository has been archived and
this is just a [long term] fork. No new features are planned, but if someone wants to improve the module, pull requests are welcome.
Magento 2 - Admin Activity
- Easily track every admin activity like add, edit, delete, print, view, mass update etc.
- Failed attempts of admin login are recorded as well. You get access to the user’s login information and IP address.
- Track page visit history of admin.
- Track fields that have been changed from the backend.
- Allow administrator to revert the modification.
Installation
-
Composer Installation
- Navigate to your Magento root folder
cd path_to_the_magento_root_directory - Then run the following command
composer require catgento/module-admin-activity - Make sure that composer finished the installation without errors.
- Navigate to your Magento root folder
-
Command Line Installation
- Backup your web directory and database.
- Download the latest Cron Scheduler installation package kiwicommerce-admin-activity-vvvv.zip here
- Navigate to your Magento root folder
cd path_to_the_magento_root_directory - Upload contents of the Admin Activity Log installation package to your Magento root directory
- Then run the following command
php bin/magento module:enable Catgento_AdminActivity
- After installing the extension, run the following command
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:flush
- Log out from the backend and log in again.
Where will it appear in the Admin Panel
Admin Activity Log
Go to System > Admin Activity > Admin Activity. Here you can See the list of admin activity logs and page visit history.

- Page Visit History

By clicking View in each admin activity log, you can see the slider with admin activity log details.
Login Activity
Go to System > Admin Activity > Login Activity. Here you can See the list of login activity logs.

Configuration
You need to follow this path. System > Admin Activity > Configuration
- General configuration
- Allow Module Section
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.1.5 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2022-01-04 12:23:17 |
| 1.1.4 | stable | Not tested | Not yet tested Details | 2021-11-30 10:23:56 |
| 1.1.3 | stable | Not tested | Not yet tested Details | 2021-11-29 15:08:52 |
| 1.1.2 | stable | Not tested | Not yet tested Details | 2020-11-27 15:48:12 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2020-11-24 13:45:13 |
| 1.0.9 | stable | Not tested | Not yet tested Details | 2020-11-24 13:42:28 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2020-11-24 12:23:04 |
| 1.0.8 | stable | Not tested | Not yet tested Details | 2020-11-24 12:01:08 |
| 1.0.7 | stable | Not tested | Not yet tested Details | 2020-06-05 08:57:32 |
| 1.0.6 | stable | Not tested | Not yet tested Details | 2019-07-12 11:34:55 |
| 1.0.5 | stable | Not tested | Not yet tested Details | 2018-10-09 11:22:06 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2018-07-02 07:13:22 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2018-06-13 12:00:57 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2018-06-09 12:18:40 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2018-06-08 12:12:15 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2018-06-08 12:12:15 |
Requires 2
| Package | Constraint |
|---|---|
| magento/framework | >=100.0.0 |
| magento/module-backend | >=100.0.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.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 543 | 9 errors, 534 warnings (ruleset: Magento2) — 268 auto-fixable with phpcbf |
| PHPMD | Warning | 38 | 38 rule violations (MissingImport:12, CyclomaticComplexity:6, ExcessiveClassComplexity:3, UnusedLocalVariable:3, UnusedFormalParameter:3) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 3 | valid; 3 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.
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
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.
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.