Methodology

How a module is checked

Every module is installed into a clean database of the matching Odoo series, built from the official odoo:<series> image, with no demo data, using -i <module> --stop-after-init. The result is the process exit code and the log.

Statuses

Status	Meaning
✓Installs	Installs
!Installs with warnings	Installs with warnings
▲Blocked by a dependency	Blocked by a dependency
~Environment problem	Environment problem
✗Install error	Install error
⏱Timed out	Timed out

What we deliberately do NOT count as incompatibility

A failure caused by a missing external Python package or a missing system utility in the image is recorded as an environment problem and is not counted against the module. The same applies when the harness itself fails to expose the module to Odoo. This is deliberate: without that separation the statistics would be untrue, and an untrue index is worth nothing.

Limits

• Paid modules cannot be installed without a licence — for those we publish metadata only.
• An install check is not a functional test: a module can install and still misbehave.
• Batch mode: on a mass pass modules are installed in groups; if a group fails, each member is retried alone. The dataset records this in the batched field.

We publish the fact of a run, with its date and log — not a rating of a vendor.

Data updated 2026-08-19 09:42 UTC · we publish the install log with a date, not a vendor rating · CSV and JSON are open

Independent project. Not affiliated with Odoo S.A. or the Odoo Community Association.