Skip to content
PluginCanary

Enable Responsive Image

by Aki Hamano · 1,000+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 25 Jul 2026, 5 releases in 24 months, no unpatched vulnerabilities.

87/ 100 Canary Score
Sub-scores for Enable Responsive Image
Ownership100
Maintenance85
Security100
Support70
Reputation70

How the score works

Quick answers

Is Enable Responsive Image still maintained?
Yes. Last release 25 Jul 2026, 5 releases in the last 24 months. 25 Jul 2026 · wordpress.org
Who owns Enable Responsive Image, and has it changed hands?
No change recorded. Main committer wildworks since Dec 2023. 3 Nov 2026 · SVN log
Was Enable Responsive Image removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Enable Responsive Image safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Enable Responsive Image update safe to install?
No ownership change before 1.7.0. No one-star spike after it. 25 Jul 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-master11 Dec 2023 to 11 Dec 2023, 1 commits
wildworks12 Dec 2023 to 4 Nov 2026, 11 commits

2 committers recorded. No ownership change since 2023.

Maintenance

Last release
3 months ago
Releases, 24 months
5
Tested up to
7.1 current
Requires PHP
8.0 supported 8.2+
Releases per quarter
Releases per quarter for Enable Responsive Image
Q1 20242
Q2 20241
Q3 20240
Q4 20241
Q1 20251
Q2 20250
Q3 20250
Q4 20251
Q1 20261
Q2 20261
Q3 20261
Q4 20260

Last release 25 Jul 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

No published vulnerabilities on record for this plugin.

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

Support

0% of 1 support threads resolved in the last 2 months.

Momentum

1,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for Enable Responsive Image
4 May 202665
11 May 2026218
18 May 2026243
25 May 2026170
1 Jun 2026224
8 Jun 2026188
15 Jun 2026635
22 Jun 2026397
29 Jun 2026315
6 Jul 2026297
13 Jul 2026437
20 Jul 2026700
27 Jul 2026447
3 Aug 2026373
10 Aug 2026412
17 Aug 2026285
24 Aug 2026249
31 Aug 2026276
7 Sep 2026318
14 Sep 2026347
21 Sep 2026531
28 Sep 2026544
5 Oct 2026440
12 Oct 2026497
19 Oct 2026666
26 Oct 2026675
2 Nov 2026108

Weekly downloads over the last 4 weeks are 31% above the 27-week average.

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.7.0
AuthorAki Hamano
Added12 Dec 2023
Last updated25 Jul 2026
Active installs1,000+
Requires WordPress7.0
Tested up to7.1.4
Requires PHP8.0
CategoryDesign & Themes > Themes & Templates
Tagsblock, image, gutenberg, responsive

Other plugins by this author: Flexible Table Block, Custom HTML Block Extension, Flexible Spacer Block, RichText Extension, Piano Block

Questions

Is Enable Responsive Image still maintained?

Yes. Last release 25 Jul 2026, 5 releases in the last 24 months.

Who owns Enable Responsive Image, and has it changed hands?

No change recorded. Main committer wildworks since Dec 2023.

Was Enable Responsive Image removed from wordpress.org?

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

Is Enable Responsive Image safe?

No known vulnerabilities on record.

Is the latest Enable Responsive Image update safe to install?

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