Download websites that use Ubercart

About Ubercart

Before Drupal had a commerce story of its own, somebody had to bolt a shopping cart onto it. Ubercart was that bolt-on, a module released in 2006 that turned a content management system into a place where products could be listed, carts filled and orders taken. Written in PHP and distributed under GPL v2, the module comes from an era when adding commerce to a site meant extending the CMS you already ran rather than sending shoppers off to a hosted checkout.

Age is the defining fact in this record, and it changes how the number should be read. As of October 2026 we detect the module on 2 sites. A count of that size, for a module of this vintage, does not describe a growing product. The population is better understood as an installed base: sites that were built once, that worked, and that nobody has had a strong enough reason to rebuild. Some are actively maintained by people who prefer a self-hosted store to a monthly subscription. Others run on a Drupal generation that stopped receiving fixes years ago, which is a different situation entirely and a considerably more urgent one.

Detection here is inferential, and the limits deserve naming. A CMS module leaves traces in URL patterns, form markup and asset paths rather than announcing itself in a response header. A store that has been heavily themed, or that sits behind a full page cache or a reverse proxy, can hide those traces well enough to fall out of the count. So the figure is a floor rather than a census, and it leans toward sites that kept the default templates, which are rarely the sites under active development.

The commercial reading follows directly. A domain in this list is a business that sells online, that owns its stack rather than renting one, and that is running commerce software from a previous decade. For a hosting company, a Drupal agency, or a vendor selling a migration path to a modern platform, that combination is a qualified lead in a way that a plain list of online stores is not. For a security team it is a population worth scanning, because unmaintained payment paths are where old vulnerabilities keep working.

Checking one domain tells you which cart it runs. The export answers the questions that need the whole set: how quickly the installed base is shrinking between snapshots, which country domains and industries are still holding on, which of the sites still take payments through the module, and which remaining stores are large enough to be worth approaching. Migration markets get sized from lists like this one, never from lookups.