jetrails / magento2-cloudflare

jetrails/magento2-cloudflare

Interact with popular Cloudflare features though Magento's backend portal

  • Rafael Grigorian
magento2-module Compatibility: 2.4.7-2.4.8 Code Quality: Fail Tests: N/A Security: Pass MIT

Magento 2 — Cloudflare — By JetRails

Interact with popular Cloudflare features though Magento's backend portal.




preview.png

Documentation

The user guide can be found here. The user guide goes through the installation process as well as explains all the features that comes with this extension. For further support, please email [email protected].

Build System

A simple Makefile is used as a build system. Run make help to see available commands.

Development Environment

We use a super simple development environment that is ephemeral. You can spin it up by doing the following:

docker compose up -d
docker compose logs -f
docker compose down # destroy environment

You can deploy the module into the development environment by running the following:

make clean
make build
make deploy

You can then access the magento container by running the following:

docker compose exec magento bash

Once in the container you can run the standard commands to install the module:

magento setup:upgrade
magento setup:di:compile

The Magento site is hosted on http://localhost and the backend can be reached at http://localhost/admin. Default user name is jetrails and default password is magento2.

No changelog yet

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

Versions
Version Stability QA Status Compatibility Released
1.4.2 stable Not tested Not yet tested Details 2024-06-20 16:03:46
1.4.1 stable Not tested Not yet tested Details 2023-04-12 19:19:19
1.4.0 stable Not tested Not yet tested Details 2022-06-23 20:29:41
1.3.9 stable Not tested Not yet tested Details 2022-06-14 13:56:50
1.3.8 stable Not tested Not yet tested Details 2022-04-06 19:35:01
1.3.7 stable Not tested Not yet tested Details 2021-11-03 17:48:47
1.3.6 stable Not tested Not yet tested Details 2021-07-23 19:05:56
1.3.5 stable Not tested Not yet tested Details 2021-07-15 18:27:28
1.3.4 stable Not tested Not yet tested Details 2021-06-07 17:56:12
1.3.3 stable Not tested Not yet tested Details 2021-04-27 16:15:42
1.3.2 stable Not tested Not yet tested Details 2020-11-24 20:55:40
1.3.1 stable Not tested Not yet tested Details 2020-10-29 15:54:29
1.3.0 stable Not tested Not yet tested Details 2020-10-14 19:13:24
1.2.6 stable Not tested Not yet tested Details 2020-06-26 19:41:34
1.2.5 stable Not tested Not yet tested Details 2020-05-18 19:47:19
1.2.4 stable Not tested Not yet tested Details 2020-05-13 16:43:53
1.2.3 stable Not tested Not yet tested Details 2020-05-07 18:37:19
1.2.2 stable Not tested Not yet tested Details 2019-10-30 13:15:31
1.2.1 stable Not tested Not yet tested Details 2019-09-16 16:44:05
1.2.0 stable Not tested Not yet tested Details 2019-09-09 14:50:33
1.1.1 stable Not tested Not yet tested Details 2019-08-15 13:52:12
1.1.0 stable Not tested Not yet tested Details 2019-08-14 14:56:47
1.0.0 stable Not tested Not yet tested Details 2018-09-13 20:31:01
1.4.3 stable Fail Magento 2.4.7-2.4.8 Details 2026-05-30 19:38:42

Requires 1

Package Constraint
php >=7.2

Requires-dev 1

Package Constraint
phpcompatibility/php-compatibility *

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 Fail di error Fail di error

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 20062 20062 warnings (ruleset: Magento2) — 19010 auto-fixable with phpcbf
PHPMD Warning 7 7 rule violations (NumberOfChildren:4, CyclomaticComplexity:2, UnusedFormalParameter:1)
Cpd Warning 1 1 duplicated chunk spanning 42 total lines (min-lines=5, min-tokens=70)
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. 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 455 455
2.4.8 455 455
2.4.9 455 455

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
Authors
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.