clawrock / magento2-debug

clawrock/magento2-debug

Magento 2 debug module based on Magento 1 Profiler with some extra features.

magento2-module Compatibility: 2.4.7 Code Quality: Warning Tests: Fail Security: Pass OSL-3.0, AFL-3.0

Are you the maintainer of clawrock?

Packagento pulls clawrock's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

Packagist
Packagist
Build Status

Magento 2 - Debug module

Module for debugging Magento 2 performance. It works without overwriting any core files and it can be installed with composer.

Installation

  1. Enable developer mode php bin/magento deploy:mode:set developer
  2. Install module via composer composer require clawrock/magento2-debug
  3. Register module php bin/magento setup:upgrade
  4. Enable profiler in configuration: Stores -> Configuration -> Advanced -> Debug
  5. Enable DB profiler php bin/magento debug:db-profiler:enable

Configuration

All settings have only default scope and config type pool is set to environment for better integration with php bin/magento app:config:dump

Compatibility

  • Magento >= 2.4.4
  • PHP >= 8.1

Profiler collectors

  • Ajax
  • Cache
  • Config
  • Customer
  • Database
  • Events
  • Layout
  • Memory
  • Models
  • Plugins
  • Request/Response
  • Performance
  • Translations

Additional features

Credits

No changelog yet

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

Versions
Version Stability QA Status Compatibility Released
2.2.1 stable Fail Magento 2.4.7 Details 2026-06-25 14:02:10
2.2.0 stable Fail Magento 2.4.7 Details 2025-11-12 10:30:24
2.1.4 stable Not tested Not yet tested Details 2023-01-31 14:13:50
2.1.3 stable Not tested Not yet tested Details 2023-01-23 16:07:26
2.1.2 stable Not tested Not yet tested Details 2023-01-02 16:57:23
2.1.1 stable Not tested Not yet tested Details 2023-01-02 15:21:22
2.1.0 stable Not tested Not yet tested Details 2023-01-02 12:12:53
2.0.3 stable Not tested Not yet tested Details 2019-05-22 21:37:41
2.0.2 stable Not tested Not yet tested Details 2019-04-03 23:45:25
1.0.0 stable Not tested Not yet tested Details 2019-01-03 20:22:05
2.0.1 stable Not tested Not yet tested Details 2019-01-01 23:47:24
2.0.0 stable Not tested Not yet tested Details 2019-01-01 23:43:56
1.1.0 stable Not tested Not yet tested Details 2018-12-08 01:42:27

Requires 8

Package Constraint
filp/whoops ^2.1
jdorn/sql-formatter ^1.2
magento/framework ~103.0
magento/module-backend ~102.0
magento/module-developer ^100.4
php >=8.1
symfony/stopwatch ^2.8 || ^3.0 || ^4.0 || ^5.0 || ^6.0 || ^7.0
symfony/var-dumper *

Requires-dev 11

Package Constraint
bitexpert/phpstan-magento ^0.31.0
dealerdirect/phpcodesniffer-composer-installer ^0.7.1
magento/magento-coding-standard *
phpcompatibility/php-compatibility ^9.3
phpmd/phpmd ^2.9.1
phpstan/phpstan ^1.11
phpstan/phpstan-phpunit ^1.1.1
phpunit/phpunit ^9.6.33
sebastian/phpcpd ^6.0.3
slevomat/coding-standard ~6.4.1
squizlabs/php_codesniffer ~3.7.2

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 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 96 96 warnings (ruleset: Magento2)
PHPMD Warning 16 16 rule violations (MissingImport:11, IfStatementAssignment:4, TooManyPublicMethods:1)
Cpd Pass 0
Composer validate Info 1 valid; 1 advisory note (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.

PHPStan results by Magento and PHP version
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

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 1 1
2.4.8 46 Error
2.4.9 Error Error

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
OSL-3.0, AFL-3.0
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.