by
Luke W
5 (1 reviews)
Upgrade Pilot – PHP Compatibility & Update Freeze Control
PHP compatibility scan, per-plugin update freeze, and alerts when a plugin changes owner, goes abandoned, or is closed for security.
Upgrade Pilot ranks #60,121 among WordPress.org plugins with 0+ active installations, a 5/5 rating from 1 reviews, and was last updated Aug 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.2
v1.0.10
Current Version v1.0.10
Updated 3 weeks ago
Last Update on 28 Aug, 2026
Refreshed 7 hours ago
Last Refreshed on
Rank
#60,121
—
No change
Active Installs
0+
-100%
KW Avg Position
94
3.5 worse
Downloads
266
+2 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(1 reviews)
Next Milestone 10
0+
10+
40,381
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
Need 9 more installs to reach 10+
Rank Changes
Current
#60,121
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
1 reviews
Overall
100%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.10
- Last Updated
- Aug 28, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.1.2
- PHP Version
- 7.4 or higher
- Author
- Luke W
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 1
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Upgrade Pilot – PHP Compatibility & Update Freeze Control
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.
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.
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.
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.
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.
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.
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.
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.
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.