WordPress tells you when a plugin has an update. It never tells you who is behind that update. Plugins get sold. Authors walk away. Maintainers are quietly added to a project. Occasionally a plugin is closed on WordPress.org for a security problem, and the copy on your site keeps running as if nothi
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.2 and PHP 7.4.
SourceWordPress plugins · Nov 21, 2026
01 / Source details
Aboutthistool.
WordPress tells you when a plugin has an update. It never tells you who is behind that update.
Plugins get sold. Authors walk away. Maintainers are quietly added to a project. Occasionally a plugin is closed on WordPress.org for a security problem, and the copy on your site keeps running as if nothing happened. In every one of those cases WordPress shows you exactly what it showed you yesterday: nothing.
Upgrade Pilot watches the things WordPress does not.
Update trust: know who is behind your next update
Every day, Upgrade Pilot takes a snapshot of the public WordPress.org record of every plugin you have installed, and compares it to yesterday’s. It tells you when:
The author changes. A plugin that just changed hands is the single clearest signal to look before you leap. Ownership transfers are how a trusted plugin becomes an untrusted one, without a single line of visible change.
New contributors appear. Someone new now has commit access to code running on your site.
A plugin is closed or removed from WordPress.org , along with the reason given. Closed plugins receive no further updates, and if the closure was for a security issue you are running known-vulnerable code.
Plugins and themes that have simply gone quiet – nobody has updated them in longer than a threshold you set – are reported in the readiness report rather than emailed to you as an alert, because abandonment is a slow fact, not an event that happened this morning.
You can then freeze automatic updates for that one plugin , so a bad release cannot install itself overnight while you decide. The freeze is per plugin, opt in, and never touches WordPress core. Manual updates always remain available. It will not help you hide from a security fix.
Upgrade readiness: know the upgrade will not break the site
Before you move to a new PHP or WordPress version, Upgrade Pilot answers whether it is safe:
Server checks. Your PHP version against WordPress’s actual minimum and against the version you plan to move to. Your database version against the requirement of the update WordPress is really being offered, read live from WordPress itself rather than from a number hardcoded by us. Memory limit, extensions, HTTPS.
PHP security support. How long the PHP branch you are running still receives security fixes.
Every plugin and theme, cross-referenced against WordPress.org. Which ones declare a PHP requirement higher than your target, which have not been tested against recent WordPress releases, which have not been updated in years, and which have been closed.
A local scan of your plugins’ PHP code , flagging what modern PHP removed or deprecated, down to the file and line. It runs in small time-sliced batches, so it does not time out, and a file that has not changed since the last scan is not analysed again.
Findings that are honest about their own certainty
Deterministic results are labelled fact . Static-analysis results are labelled advisory , and never drive the verdict on their own, because version-guarded code and unreachable branches legitimately trigger them. Anything you have inspected and cleared can be suppressed permanently, and the suppression survives future scans.
Read only, always
Upgrade Pilot never updates, deactivates, installs, or rewrites anything. The one thing it can change is a per-plugin automatic-update hold, and only when you click the button yourself.
Also included
Site Health integration
Dashboard summary widget
Email alerts: immediate for critical events, a daily digest for warnings (informational events stay in the UI)
A REST endpoint for dashboards and fleet tooling: GET /wp-json/upgrade-pilot/v1/report , available to administrators (the manage_options capability; super admins on a network)
Works on multisite
On a WordPress network, Upgrade Pilot runs at network level, because that is where the truth is: a network shares one copy of each plugin’s files, so who wrote a plugin, whether it was closed, and whether its updates are held are facts about the whole network, not about one subsite. The free version installs network-wide, stores its data once, and is managed by a super admin from the Network Admin screens. Freezing a plugin’s automatic updates holds it across the network, because there is only one copy of the file to hold.
Upgrade Pilot Pro
Pro adds the things you need when the site belongs to someone else:
A branded, white-label client report (PDF/print) – your name, your colour, no product footer.
The readiness summary emailed to your client, on a schedule you choose, to as many addresses as you like – and you are told if it fails to send.
Slack and webhook alerts for update-trust events.
Automatic update-hold policies: hold a plugin’s automatic updates for a cooling-off period the moment it changes owner or gains a contributor.
Daily and twice-daily re-scans.
On a network, the Network Overview: every subsite’s readiness and update-trust status on one screen, and – the question you actually have when a plugin changes hands – exactly which of your sites are running it.
A private email channel with the developer.
Four things are free that people usually assume are paid, so they are worth saying plainly.
The machine-readable export is free. WP-CLI --format=json and the REST endpoint are part of the free version and are not gated, metered or licence-checked.
The digest email is free. The free version already emails you, the site administrator, immediately when a plugin is closed or flagged, and a daily digest of everything else. What Pro adds is sending the readiness summary to other people – your client – on a schedule you pick, and telling you when a send fails.
The weekly re-scan is free , and on by default. What Pro adds is running it daily or twice daily.
Multisite is free, in full. Upgrade Pilot installs network-wide, stores its data once, is managed by a super admin from the Network Admin screens, and a freeze holds across the whole network. What Pro adds on a network is the Network Overview screen described above – not multisite itself.
Freezing a plugin by hand is free too. What Pro adds is doing it automatically, on a policy.
Every paid tier includes every feature; tiers differ only by how many sites your licence covers. On a network, each subsite counts as one of those sites, and you activate the licence once from Network Admin to cover them all.
Pro is a separate download, not an in-place upgrade. When you buy or start a trial you download the Pro build and upload it like any other plugin; it installs alongside this free copy, and activating it switches the free copy off for you. Your settings, scan history and freeze list carry over untouched.
External services
Upgrade Pilot uses WordPress.org, always. It uses Freemius – who sell and license the paid version – only when you go looking for the paid version, and only in the four situations listed below.
1. WordPress.org Plugin and Theme API (api.wordpress.org) This is the plugin’s data source and is always used. What is sent: the public slug of a plugin or theme installed on your site. Nothing else. No site URL, no user data, no configuration. The requests identify themselves only as “UpgradePilot/” followed by the plugin version. When: when you run a readiness scan, and once daily as part of the update-trust snapshot that detects author changes, new contributors, closures, and abandonment. Why: to read the public directory record for that plugin (author, contributors, last updated, tested-up-to, required PHP, and whether it has been closed). Note: WordPress core already contacts this same API for its own update checks. How much: plugin lookups are batched – every plugin on the site is asked for in a single request, so a 40-plugin site makes one plugin request, not forty. The theme API has no batch mode, so themes cost one request each. Answers are cached for 24 hours (72 hours for “not in the directory”), and 429 or 5xx responses trigger a backoff that later calls respect. A typical 40-plugin, 3-theme site therefore makes about four or five requests a day in total. Privacy: https://wordpress.org/about/privacy/ WordPress.org publishes a privacy policy but no separate terms-of-use document for this API. It is the same public API, on the same host, that WordPress core itself queries for update checks.
2. Freemius (freemius.com), who sell and license Upgrade Pilot Pro Freemius is contacted in four situations. Every one of them is something you click. It is never contacted in the background.
You opt in, start a trial, or activate a licence. Sent to api.freemius.com: your site URL, your WordPress and PHP versions, and the email address of the account you activate with. This only happens after you explicitly opt in on the activation screen, or when you start a trial or activate a licence.
You open the “Upgrade” page. The plugin adds an “Upgrade” item to its own menu, and the Reports & Automation screen links to it. Opening that page asks Freemius for the current plan prices so it can show them to you (api.freemius.com), and that request carries your site URL. Nothing else is sent. This happens whoever you are, including if you skipped the opt-in – but only when you open that page. If you never open it, it never runs. That request is made by your own server, not by your browser: the page talks to your site’s admin-ajax, and your site talks to Freemius. The page itself loads no third-party scripts at all. Everything it renders – the plan table, the icons, the payment-brand badges – is served from this plugin’s own folder. The payment SDK’s bundled pricing script used to inject Google Analytics and a remote checkout script into your dashboard on that page; this build removes both, along with the SDK’s remaining remote references (all four modifications are listed under “Source code” below).
You click “Contact Us”. That opens F
See it in action
Screenshots & previews.
Update trust: ownership changes, closures, and abandoned plugins, with per-plugin update freezeThe readiness report: server checks and the WordPress.org cross-referenceStatic PHP compatibility findings, with per-finding suppressionSite Health integrationSettings
02 / Source details
Frequently asked questions.
Does this plugin block updates?
No, not by default, and never silently.
Upgrade Pilot ships with nothing frozen. It changes no update behaviour at all until you personally decide to hold one specific plugin, which you would typically do right after it tells you that plugin just changed owners or was closed on WordPress.org.
When you do freeze a plugin:
It holds automatic updates for that one plugin only , using WordPress’s standard per-plugin auto-update filter.
WordPress core is never affected. Upgrade Pilot registers no core-update filter of any kind, and does not disable the automatic updater. Core updates behave exactly as they would without this plugin installed.
The update is never hidden. It still appears on your Plugins screen exactly as normal. You simply see a note explaining why it is being held, and you can install it manually at any time.
It will not hide a security fix from you. If a plugin you have frozen is then closed on WordPress.org for a security issue, Upgrade Pilot says so loudly and tells you to unfreeze and update. Freezing is a pause for thought, not a place to hide.
You can unfreeze any plugin with one click, and uninstalling Upgrade Pilot removes all freeze state.
Why should I care who owns a plugin?
Because ownership changes are invisible in your dashboard, and they change who can push code to your site. A plugin can be sold, or hand a new maintainer commit access, and the next automatic update arrives looking exactly like every previous one. Upgrade Pilot exists to put a name and a date on that moment, so you can decide whether to let the update through.
Is my site ready for the next WordPress or PHP version?
Run the readiness report. It checks your server against the requirements WordPress itself reports, cross-references every plugin and theme against its WordPress.org record, and scans your plugins’ PHP code for anything modern PHP removed.
Will the scan slow down or time out on shared hosting?
No. The code scan processes files in small time-sliced batches with hard budgets, driven from your browser while you watch and by WP-Cron in the background. Oversized and vendored files are skipped, and that is disclosed in the results rather than hidden.
Does the scanner send my code anywhere?
No. The code scan runs entirely on your own server. See the External services section above for the complete list of what leaves your site, which is only public plugin slugs.
What does “advisory” mean next to a finding?
It means the finding came from reading your code rather than from a definitive fact, and might be a false positive: code behind a version check, a dead branch, or a bundled polyfill can all trigger one. Advisory findings never turn your verdict red on their own, and you can suppress any that you have checked.
Does it work on a multisite network?
Yes. Network activate it, and it is managed by a super admin from the Network Admin menu. Because a network shares one copy of each plugin’s files, Upgrade Pilot keeps one set of data for the whole network rather than one per subsite, which also means it makes the same small number of requests to WordPress.org whether your network has three sites or three hundred. Freezing a plugin holds its automatic updates across the network, since there is only one copy of the file.
How do I get support?
Free support is the WordPress.org support forum for this plugin. I am one person, and I read every thread.
Licence holders also get a private email channel with me, which is the right place for anything you would rather not post in public: client site details, server configuration, or a scan result that shouldn’t be pasted into a forum. The address is shown inside the plugin once a licence is active.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati