Download websites that use Jilt plugin

About Jilt plugin

A WordPress plugin gets installed once and then, very often, is never thought about again. The store keeps selling, the plugin keeps loading its assets on every page, and the decision that put it there recedes further into the past with each year. Which is why plugin data reads less like a snapshot of what merchants are choosing now and more like a sediment layer of what they chose once and never revisited.

Jilt plugin sits in that sediment. Filed under Cart abandonment, written in PHP, dating to 2014 and distributed through the public WordPress plugin directory until that listing was closed at the author's request, the plugin does the job every WooCommerce store eventually wants done, which is chasing the shoppers who filled a cart and then left. A store carrying cart recovery has also moved past the stage of simply having a catalogue online. Somebody is measuring abandonment, somebody is sending email, and order volume is high enough for recovery to be worth automating.

The licensing line rewards careful reading rather than literal reading. Our index records the entry as Proprietary, even though the distribution channel was a directory of freely downloadable code. What that combination usually describes is the shape of a business rather than the shape of the code: a free connector plugin in the directory, a paid hosted service behind it, and a vendor, SkyVerge, whose name is not the name on the plugin.

Server-side code is hard to see from outside. A PHP plugin runs inside the store and finishes its work before the browser receives anything, so detection depends on traces left in public output, such as an enqueued script path carrying the plugin slug, an asset URL with a version string attached, or a form field with a recognisable name. As of October 2026 we match 4 sites that way, and stores that strip, concatenate or rename their assets are not among them.

Version data is the part with real analytic value. We record 4 distinct versions still in the wild, with 1.7.12 recurring across the matched stores, and a spread like that on a plugin of this vintage says something plain about maintenance. Merchants running aging email tooling rarely notice that it has aged, which is precisely why an enumerated list of them is commercially useful to anyone selling a replacement. A store owner checking a single domain wants to know what a competitor's cart recovery runs on. An agency or a rival vendor wants the opposite, every store still carrying the old integration, with its version attached, so outreach can be aimed at installs that are genuinely stale rather than at WooCommerce shops in general. Nothing in the WordPress ecosystem publishes that population. The pages themselves do.