Open source · Catalog

Magento 2 Extension Atlas

Every public Magento 2 module, theme and related project with a push or a Packagist release between 2024-10-11 and 2026-10-11. Forks, archived and private repositories are excluded. Data harvested 2026-10-11, refreshed periodically.

Read the landscape guide Magendoo's own modules →

Search, filter and sort below. Copy any filtered view as CSV.

7,769 entries

4,140 on Packagist

3,629 not on Packagist

137 in a curated list

740 10+ stars

5,807 no GitHub topics

7,769 matching showing 1–100

Method

How was this catalog gathered?

Three sources, merged by repository. An entry is "active" when it had a push or a Packagist release in the two years before the harvest date.

GitHub search

14 queries: magento2, magento-2, "magento 2", magento and mage-os in the name, description or topics, plus the topics magento2-module, magento2-extension, adobe-commerce, hyva and mage-os. Each query was split into date windows so no single query hit GitHub's 1,000-result cap.

Packagist

All 11,810 packages of type magento2-module, magento2-theme, magento2-component and magento2-library, with their last release date. Packages hosted on GitHub were matched to their repository.

Curated lists

Links from public curated lists of Magento 2 extensions, used only to find candidates and to mark entries as listed. The lists themselves are not extensions and are not entries in the catalog.

Repository details

Stars, topics and last push come from the GitHub API. "Last activity" is the later of the last push and the last Packagist release. "Kind" is the Packagist type when there is one, otherwise a guess from the name and topics.

Questions about the atlas

What counts as an active Magento 2 extension here?

A public, non-fork, non-archived repository or Packagist package of a Magento 2 module, theme, component, library or related project that had a git push or a Packagist release between 2024-10-11 and 2026-10-11. Activity, not popularity, is the only entry criterion.

Why is a module I know missing?

Usually because it is a fork, is archived, is private, or had no push or release in the last two years. A repository that never mentions Magento in its name, description or topics and is not on Packagist can also be missed. Send the repository URL to [email protected] and it will be checked for the next refresh.

What does "not on Packagist" mean for a module?

The repository was found on GitHub but no Packagist package of type magento2-module, -theme, -component or -library points to it. Such modules cannot be installed with composer require from the public registry; they need a VCS repository entry or a manual copy.

Does a high star count mean the module is good?

No. Stars measure visibility, and visibility in this ecosystem depends mostly on topics, Packagist presence and curated lists. Check last activity, a tagged stable release, the supported Magento versions in the README and the license before you depend on anything.

How often is the catalog refreshed?

Periodically, by re-running the same harvest. The harvest date is stated in the introduction; every refresh replaces the whole dataset rather than patching entries.

How are the categories assigned?

A language model gives each entry one primary category from a fixed list, the storefront stack it targets (Hyvä, Breeze, PWA or headless, Mage-OS, Adobe Commerce only) and up to five tags. The result is checked against a reference sample labelled independently of the model, and entries without enough information stay Uncategorised rather than getting a guessed label. If an entry is in the wrong category, write to [email protected] and it will be corrected.

Context

Why good modules stay invisible.

The companion guide walks through what this data shows about the open-source Magento 2 ecosystem in 2026, and what a maintainer should change to be found.

Read the landscape guide → Magendoo's open-source work