Plugin profile · observed daily since 02 Aug 2026
Travelpayouts
Active installs6,000+ rounded
Current authorTravelpayouts
Owner changesNone while we have been watching
Last release1 month ago 04 Aug 2026
Support0 / 1 resolved, last 2 months
Releases on record55
Rating4.4 /5 · 17
Added to directory19 Aug 2015
Requires WPfalse
Requires PHPfalse
Version lag—
Tested up toWP — not declared
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Travelpayouts throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| travelpayouts | 55 | 04 Jul 2017 | 04 Aug 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Moderately adopted: 6,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
38 downloads a day over the last 7 days, falling 36% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 328/day09 Sep 2026
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep | 09 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 63 | 44 | 57 | 38 | 92 | 55 | 48 | 47 | 0 | 44 | 33 | 49 | 47 |
Unchanged throughout: ratings total (17) · active installs (6,000+) · version (1.2.3) · support threads (1) · threads resolved (0)
39 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory11 years ago 19 Aug 2015
Requires WPfalse
Requires PHPfalse
Version lag—
Is anyone still maintaining this?
- Last released 04 Aug 2026, 37 days ago.
- Does not declare which WordPress version it has been tested against. A field the author sets themselves, so it is left blank rather than reported wrong.
- 0 of 1 support threads answered in the last two months.
- The same account maintains 1 other plugin, and none has been updated in over a year, the most recent on 07 Oct 2015.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 04 Aug 20261 month agoVersion 1.2.3 released
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 26 Feb 20266 months agoVersion 1.2.2 released
- 24 Oct 202511 months agoVersion 1.2.1 releasedfrom the release logCommitted by travelpayouts.
- 20 Oct 202511 months agoVersion 1.1.23 releasedfrom the release logCommitted by travelpayouts.
- 20 Oct 202511 months agoVersion 1.2.0 releasedfrom the release logCommitted by travelpayouts.
- 27 May 202515 months agoVersion 1.1.22 releasedfrom the release logCommitted by travelpayouts.
- 22 Apr 202517 months agoVersion 1.1.21 releasedfrom the release logCommitted by travelpayouts.
- 07 Oct 202423 months agoVersion 1.1.20 releasedfrom the release logCommitted by travelpayouts.
- 10 Sep 20241.5 years agoVersion 1.1.19 releasedfrom the release logCommitted by travelpayouts.
- 23 Jul 20242 years agoVersion 1.1.18 releasedfrom the release logCommitted by travelpayouts.
- 24 May 20242 years agoVersion 1.1.17 releasedfrom the release logCommitted by travelpayouts.
- 22 May 20242 years agoVersion 1.1.16 releasedfrom the release logCommitted by travelpayouts.
- 06 Mar 20242.5 years agoVersion 1.1.15 releasedfrom the release logCommitted by travelpayouts.
- 24 Jan 20242.5 years agoVersion 1.1.14 releasedfrom the release logCommitted by travelpayouts.
- 04 Jul 20179 years ago41 earlier releasesfrom the release logBetween 04 Jul 2017 and 23 Jan 2024. Listed individually in the public release log rather than here.
- 19 Aug 201511 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Travelpayouts for all 39 days we have observed it.
- It was last released 1 month ago (04 Aug 2026).
- WordPress.org reports 6,000+ active installs.
- It carries 17 ratings, averaging 4.4 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Reach out about this record
Corrections, missing context, or anything else about Travelpayouts: a person reads every submission, and corrections get a reply within 5 business days.