Skip to content
PluginCanary

Bulgarisation for WooCommerce

Fewer than 10 active installs · Checked 3 Nov 2026
Avoid1 Warning

Avoid: Bulgarisation for WooCommerce is closed on wordpress.org and no longer gets updates.

10/ 100 Canary Score

Capped at 10: the plugin is closed on wordpress.org.

Sub-scores for Bulgarisation for WooCommerce
Ownership100
Maintenance10
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Bulgarisation for WooCommerce still maintained?
No. Closed on wordpress.org on 24 Sep 2026. 24 Sep 2026 · wordpress.org
Who owns Bulgarisation for WooCommerce, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist. 3 Nov 2026 · SVN log
Was Bulgarisation for WooCommerce removed from wordpress.org?
Yes. Closed on 24 Sep 2026, reason: reason not stated. 24 Sep 2026 · wordpress.org
Is Bulgarisation for WooCommerce safe?
2 known vulnerabilities, all fixed (latest in 3.0.15). Not on the exploited list. 12 Mar 2024 · Wordfence Intelligence
Is the latest Bulgarisation for WooCommerce 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.

  • WarningCLS-1Closed on wordpress.org on 24 Sep 2026, reason: reason not stated. Replace this plugin. It no longer receives updates from wordpress.org.24 Sep 2026Evidence

Ownership timeline

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

No ownership change recorded. Commit history is collected for plugins with 1,000+ installs or on a watchlist.

Maintenance

Last release
not recorded
Releases, 24 months
0
Tested up to
not stated vs 7.1
Requires PHP
not stated supported 8.2+

Release history builds as we see new versions.

Reputation

Last 90 days: no reviews.

Security record

2 vulnerabilities on record, all patched (latest fixed in 3.0.15).

Show 2 patched vulnerabilities
PublishedIssueCVSSAffectedFixed inDays to patch
12 Mar 2024Bulgarisation for WooCommerce <= 3.0.14 - Cross-Site Request Forgery7.3<= 3.0.143.0.15n/a
12 Mar 2024Bulgarisation for WooCommerce <= 3.0.14 - Missing Authorization7.3<= 3.0.143.0.15n/a

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

Support

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

Momentum

Fewer than 10 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

Versionnot stated
Authornot stated
Addednot stated
Last updatednot stated
Active installsFewer than 10
Requires WordPressnot stated
Tested up tonot stated
Requires PHPnot stated
CategoryShipping & Logistics > Shipping Rate Calculators
Tagsnot stated

Questions

Is Bulgarisation for WooCommerce still maintained?

No. Closed on wordpress.org on 24 Sep 2026.

Who owns Bulgarisation for WooCommerce, and has it changed hands?

Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.

Was Bulgarisation for WooCommerce removed from wordpress.org?

Yes. Closed on 24 Sep 2026, reason: reason not stated.

Is Bulgarisation for WooCommerce safe?

2 known vulnerabilities, all fixed (latest in 3.0.15). Not on the exploited list.

Is the latest Bulgarisation for WooCommerce 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 3 Nov 2026.Report a data issue