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.

APG Withdrawal for WooCommerce

by Art Project Group · 60+ active installs · Checked 3 Nov 2026
Limited data

Limited data: APG Withdrawal for WooCommerce has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

100/ 100 Canary Score

Based on 3 of 5 areas

Sub-scores for APG Withdrawal for WooCommerce
Ownership100
Maintenance100
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is APG Withdrawal for WooCommerce still maintained?
Yes. Last release 29 Oct 2026, 13 releases in the last 24 months. 29 Oct 2026 · wordpress.org
Who owns APG Withdrawal for WooCommerce, and has it changed hands?
No change recorded. Main committer artprojectgroup since May 2026. 3 Nov 2026 · SVN log
Was APG Withdrawal for WooCommerce removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is APG Withdrawal for WooCommerce safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest APG Withdrawal for WooCommerce update safe to install?
No ownership change before 0.8.0. No one-star spike after it. 29 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
plugin-master16 May 2026 to 16 May 2026, 1 commits
artprojectgroup17 May 2026 to 29 Oct 2026, 21 commits

2 committers recorded. No ownership change since 2026.

Maintenance

Last release
6 days ago
Releases, 24 months
13
Tested up to
7.2 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for APG Withdrawal for WooCommerce
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20267
Q3 20264
Q4 20262

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

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

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

Security record

No published vulnerabilities on record for this plugin.

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

Support

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

Momentum

60+ 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

Version0.8.0
AuthorArt Project Group
Added17 May 2026
Last updated29 Oct 2026
Active installs60+
Requires WordPress6.0
Tested up to7.2
Requires PHP7.4
Categorynot stated
Tagsrefund, withdrawal, woocommerce, consumer rights, right of withdrawal

Other plugins by this author: WC - APG NIF/CIF/NIE Field, WC - APG Weight Shipping, WC - APG Free Shipping, APG Google Image Sitemap Feed, APG Google Video Sitemap Feed, WC - APG SMS Notifications, WC - APG City, Custom Base Terms, APG Legal Guarantee Notice, APG GDPR texts for forms

Questions

Is APG Withdrawal for WooCommerce still maintained?

Yes. Last release 29 Oct 2026, 13 releases in the last 24 months.

Who owns APG Withdrawal for WooCommerce, and has it changed hands?

No change recorded. Main committer artprojectgroup since May 2026.

Was APG Withdrawal for WooCommerce removed from wordpress.org?

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

Is APG Withdrawal for WooCommerce safe?

No known vulnerabilities on record.

Is the latest APG Withdrawal for WooCommerce update safe to install?

No ownership change before 0.8.0. 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