Greenskeeper
by Tony Zeoli 0 (0 reviews)

Greenskeeper

Manage WordPress updates, filter comment spam, send branded email reports, and configure SMTP delivery — for single sites and Multisite networks.

Greenskeeper ranks #62,727 among WordPress.org plugins with 0+ active installations, is #2,868 of 3,634 in the Communication category, and was last updated Oct 14, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.2
v2.4.6 Current Version v2.4.6
Updated 2 weeks ago Last Update on 14 Oct, 2026
Refreshed 2 days ago Last Refreshed on
#2,868 of 3,634 in Communication Actively maintained
View on WordPress.org
Rank
#62,727
— No change
Active Installs
0+
-100%
KW Avg Position
N/A
— No change
Downloads
2K
+2 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 20%
0+ 10+
35,159
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 8 more installs to reach 10+

Rank Changes

56,944 58,942 60,940 62,938 64,936 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
47,500 54,124 60,747 67,371 73,994 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Current #62,727
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
0 10 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Greenskeeper

Greenskeeper includes a built-in "Disable All Auto-Updates" feature available in two places. On the Updates page, an amber warning banner appears whenever any plugins or themes have auto-updates enabled, showing the exact count and a "Disable All Auto-Updates" button. On the Settings page, the Auto-Updates card shows the current status — green if all auto-updates are disabled, amber if any are enabled — with the same disable button. Clicking either button disables auto-updates for all plugins and themes in one action and logs the change to the Site Activity Log. A green confirmation card then appears with instructions for re-enabling individual auto-updates via the WordPress Plugins admin screen. The feature works on both single site and multisite WordPress installations.
WordPress auto-updates run silently in the background, bypassing Greenskeeper's update log and client reports. When a plugin auto-updates without going through Greenskeeper, the change is not recorded in the Update Log and will not appear in email reports sent to your clients. Disabling auto-updates ensures that every update on a site goes through Greenskeeper's documented, deliberate workflow — giving you full control over when updates run, a complete audit trail, and accurate client reports.
In June 2026 WordPress.org introduced a mandatory up-to-24-hour hold on all new plugin and theme updates as part of its "Protect The Shire" initiative. An AI security scanner reviews code changes during this window before they are distributed to sites with automatic updates enabled. The policy was introduced in response to a rise in AI-accelerated supply chain attacks targeting open-source plugin repositories. Greenskeeper users are largely unaffected by this delay. The 24-hour hold applies to automatic background updates — Greenskeeper's workflow is the opposite of that. Every update you run through Greenskeeper is deliberate, manually triggered, and documented with a full audit trail. You are not waiting for WordPress to push an update to your site; you are deciding when and what to update. The one area where the delay is felt is in update discovery — a new plugin release or security patch may not appear on Greenskeeper's Updates page for up to 24 hours after the developer publishes it, because WordPress.org holds the release in its review queue before making it available via the update API. If you need to apply a critical security patch before it appears in the update queue, you can install the updated plugin manually by downloading it directly from the developer and uploading it via SFTP or the WordPress plugin upload screen. Greenskeeper's Update Log and Email Reports pages support manual update entries so the patch can still be documented and reported to your client even
Yes — from v2.3.1 onward, the Email Reports page includes a "Preview Email" button next to the Send button. Clicking it opens a full-fidelity preview of the email in a modal window, rendered exactly as it will appear to the client — including the current update note, any manual entries you have added, and all session update data. The preview reflects the live state of the form, so if you add a note and click Preview, the note appears in the preview immediately. From the preview modal you can: click "Send Email" to send without closing the modal, click "Go to Updates →" to return to the Updates page if something needs to be retried, or click "Close & Edit" to return to the form and make changes before sending.
From v2.3, Greenskeeper checks whether the item already has a successful update record in the current session before running the update again. If it does, an amber informational notice appears explaining the item
to force a fresh check. The item is counted as successful so the batch completion state is not affected.
Greenskeeper dismisses the WordPress "update available" admin banner after a successful core update by clearing the update_core transient. It then shows its own confirmation notice — "WordPress X.X updated successfully" — which auto-dismisses after 4 seconds. This prevents the WordPress banner from persisting and confusing the admin into thinking the update needs to be retried.
No — from v2.2.1 onward, Greenskeeper is always the sender of record for its own emails by default. It applies its SMTP configuration only to emails it initiates (maintenance reports, admin notifications, test emails) and never interferes with WooCommerce, contact forms, password resets, or any other plugin's mail. When Greenskeeper detects another SMTP plugin on the site, it shows an informational notice on the SMTP settings card naming the plugin and confirming Greenskeeper is operating independently. If you prefer to hand delivery to the detected plugin, a checkbox on the settings card lets you do that — with a clear warning that a failure in that plugin may prevent Greenskeeper reports from sending and will not appear in Greenskeeper's email log.
Greenskeeper detects the following SMTP plugins: WP Mail SMTP, FluentSMTP, Post SMTP, Postman SMTP, Easy WP SMTP, Brevo (Sendinblue), Gravity SMTP, WP Offload SES, and Gmail SMTP. Detection covers both site-activated and network-activated installations on multisite.
Yes — from v2.1.11 onward, Greenskeeper includes a System Info page (Greenskeeper → System Info in the WordPress admin sidebar). It displays your full server environment (PHP version, extensions, server software), WordPress environment (version, URLs, memory limit, debug mode, database), active theme, and a complete list of active plugins with versions and authors. A sticky copy-and-paste panel lets you copy the full report as plain text to include in support tickets to plugin or theme developers.

Sign In / Register

You need to sign in or register to use this feature.