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.

Opal Estate Custom Fields

by wpopal · 30+ active installs · Checked 4 Nov 2026
Limited data1 Critical1 Warning

Limited data: Opal Estate Custom Fields has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

59/ 100 Canary Score

Capped at 59: a Critical signal is open.

Sub-scores for Opal Estate Custom Fields
Ownership100
Maintenance0
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Opal Estate Custom Fields still maintained?
No. Last release 12 Oct 2020, over 6 years ago. 12 Oct 2020 · wordpress.org
Who owns Opal Estate Custom Fields, and has it changed hands?
No change recorded. 4 Nov 2026 · SVN log
Was Opal Estate Custom Fields removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
Is Opal Estate Custom Fields safe?
No known vulnerabilities on record. 4 Nov 2026 · Wordfence Intelligence
Is the latest Opal Estate Custom Fields update safe to install?
Not enough data. No release date on record for the current version. Release history

Active signals

Facts we detected, with links to the source.

  • CriticalMNT-1No release in 73 months (last release 12 Oct 2020). Plan a replacement if the plugin is important to your site.12 Oct 2021Evidence
  • WarningMNT-2Tested up to WordPress 5.2.30, 19 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

Ownership timeline

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

Committers and their active periods
plugin-master28 Oct 2019 to 28 Oct 2019, 1 commits
wpopal29 Oct 2019 to 12 Oct 2020, 9 commits

2 committers recorded. No ownership change since 2019.

Maintenance

Last release
6 years ago
Releases, 24 months
0
Tested up to
5.2 vs 7.1
Requires PHP
5.6 supported 8.2+

Last release 12 Oct 2020. Tested up to 5.2, 19 major versions behind WordPress 7.1. Release history builds as we see new versions.

Reputation

Last 90 days: no reviews.

Rating distribution
5 star0
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

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

Version1.0.5
Authorwpopal
Added29 Oct 2019
Last updated12 Oct 2020
Active installs30+
Requires WordPress4.9
Tested up to5.2.30
Requires PHP5.6
Categorynot stated
Tagsestate, opalestate_addon, opal estate custom fields

Other plugins by this author: GG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels, Opal Service, Opal Woo Custom Product Variation, Opal Mega Menu, Opal Portfolio, GG Multiple Payment Routing for WooCommerce - Split and manage PayPal, Stripe accounts, Wpopal Medical, Opal Product Collection for WooCommerce, Opal Upsale Quantity for Woocommerce, OPAL SOCIAL LOGIN, GTG Product Blocks, GG eBay Management

Questions

Is Opal Estate Custom Fields still maintained?

No. Last release 12 Oct 2020, over 6 years ago.

Who owns Opal Estate Custom Fields, and has it changed hands?

No change recorded.

Was Opal Estate Custom Fields removed from wordpress.org?

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

Is Opal Estate Custom Fields safe?

No known vulnerabilities on record.

Is the latest Opal Estate Custom Fields update safe to install?

Not enough data. No release date on record for the current version.

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