Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

UniPAY Payment Gateway For WooCommerce

by unipaydev · 100+ active installs · Checked 3 Nov 2026
Limited data

Limited data: UniPAY Payment Gateway For WooCommerce has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

98/ 100 Canary Score
Sub-scores for UniPAY Payment Gateway For WooCommerce
Ownership100
Maintenance100
Security95
SupportNo data
ReputationNo data

How the score works

Quick answers

Is UniPAY Payment Gateway For WooCommerce still maintained?
Yes. Last release 22 Oct 2026, 1 release in the last 24 months. 22 Oct 2026 · wordpress.org
Who owns UniPAY Payment Gateway For WooCommerce, and has it changed hands?
No change recorded. Main committer unipaydev since Aug 2018. 3 Nov 2026 · SVN log
Was UniPAY Payment Gateway For WooCommerce removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is UniPAY Payment Gateway For WooCommerce safe?
1 known vulnerability, fixed (latest in 2.4). Not on the exploited list. 26 Oct 2026 · Wordfence Intelligence
Is the latest UniPAY Payment Gateway For WooCommerce update safe to install?
No ownership change before 2.4. No one-star spike after it. 22 Oct 2026 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
unipaydev13 Aug 2018 to 22 Oct 2026, 40 commits

1 committer recorded. No ownership change since 2018.

Maintenance

Last release
13 days ago
Releases, 24 months
1
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for UniPAY Payment Gateway For WooCommerce
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20261

Last release 22 Oct 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star5
4 star0
3 star0
2 star0
1 star0

Security record

1 vulnerability in 24 months, patched (latest fixed in 2.4).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
26 Oct 2026UniPAY Payment Gateway For WooCommerce <= 2.3 - Unauthenticated Arbitrary Order Status Manipulation5.3<= 2.32.4Patched before disclosure

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

100+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version2.4
Authorunipaydev
Added13 Aug 2018
Last updated22 Oct 2026
Active installs100+
Requires WordPress6.0
Tested up to7.1.4
Requires PHP7.4
Categorynot stated
TagsUniPAY, georgia, payment, credit card, woocommerce

Questions

Is UniPAY Payment Gateway For WooCommerce still maintained?

Yes. Last release 22 Oct 2026, 1 release in the last 24 months.

Who owns UniPAY Payment Gateway For WooCommerce, and has it changed hands?

No change recorded. Main committer unipaydev since Aug 2018.

Was UniPAY Payment Gateway For WooCommerce removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is UniPAY Payment Gateway For WooCommerce safe?

1 known vulnerability, fixed (latest in 2.4). Not on the exploited list.

Is the latest UniPAY Payment Gateway For WooCommerce update safe to install?

No ownership change before 2.4. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue