The module only reads. It modifies no files, changes no settings, and writes nothing to PrestaShop's tables beyond storing its own analyses. You can run it on production without worry — which is exactly where you need it, because the real environment is the one with the real modules and the real hosting.

It does not tell you “there is a problem with your modules”. It tells you which module, in which file, on which line, what value it found and what it recommends doing. Every rule has its identifier, its confidence level and a link to the documentation.

That matters when you have to take it up with a module vendor or justify a quote to a client.

Each finding carries a cost in effort points, and the total gives you a sense of the size of the migration: from “an afternoon” to “more than three weeks”. That is what lets you quote without guessing.

The action plan comes out as a PDF with tasks ordered by priority, the modules affected by each, and their effort. It is a presentable document: send it as it is and it reads fine without knowing PrestaShop.

Every analysis is kept. You can run it again after fixing things and compare the two to see what you have solved and what is still open. Useful for showing progress over the course of a project.

Environment: PHP version, MySQL or MariaDB version, extensions, server limits.
Core: PrestaShop version and the upgrade path you actually need.
Modules: version 9 compatibility, PHP functions that no longer exist, removed hooks, secrets hardcoded in the source.
Overrides: which ones exist and how far they have drifted from the original class.
Hooks: the ones removed or deprecated in 9.
Database: size, tables and what tends to cause trouble on upgrade.

The rule base ships inside the module, signed and version-numbered. It needs no connection to run an analysis: if it looks for a newer rule set and does not find one, it carries on with the one it came with. Compatible from PrestaShop 1.7.6 through 9.