WP Update Radar

For WordPress site owners and agencies · one plugin, one exact version

Read the release before you install it.

Release check

free · no account

Type to search the tracked set, or enter any of the 1000 slugs directly.

The exact version matters: evidence is attributed release by release, so 10.9.0 and 10.9.1 are different questions.

What this reads: public wordpress.org support threads for that release. What it cannot see: your site, your theme, your premium plugins or your PHP version. It records one aggregate counter per day, channel, tool and outcome — no plugin, no version, no address, no identity.

Or start from a site

1000 plugins tracked so far, last swept 2026-10-13. Anything outside that set returns NO READ — this covers the most-installed plugins, not all of wordpress.org.

What the check reads

Name the plugin and the exact version. This reads the public wordpress.org support forums for that release, weighs it against the plugin's own normal, and hands back a bounded reading with the threads it rests on.

  • No account, no key
  • Public forum evidence only
  • A reading, not a guarantee
a reading, stacked
  1. 01The exact version you are moving to — not the plugin in general.
  2. 02What the forums actually said about that release, counted.
  3. 03The steps that follow from it, in order.

Five readings, and what each one rests on

Two of them mean this service does not know. They are kept separate from the others on purpose — an update called safe on missing evidence is the failure this exists to prevent.

Findings — the forums said something

Non-findings — this service does not know

These two are never folded into a finding. Neither one says the release is fine.

Where the evidence stops

Each rung is a different kind of knowing, and they do not add up to certainty. The bottom two are what a free release check reads today; the top two are what a change-set pack would add.

  1. RUNG 1

    Public community signal

    Support threads on wordpress.org naming a version, counted against that plugin's own normal volume.

    Bounded by who bothers to post. Most people who hit a problem never do, so quiet is weak evidence rather than good news.

  2. RUNG 2

    Developer-declared metadata

    What the plugin itself declares: tested-up-to, required WordPress and PHP versions, last update.

    Bounded by self-reporting. Nobody verifies these fields, and a stale one is common.

  3. RUNG 3

    Limited environment input

    The WordPress and PHP versions you are on, and the set of plugins you are actually changing.

    Bounded by what you supply. Nothing is read from your site.

  4. RUNG 4

    Not tested

    Premium and private plugins, custom code, mu-plugins, themes, host caching, external services, your live data.

    Never reproduced. This rung stays unknown and is reported as such rather than assumed to be fine.

A whole change-set, not one plugin at a time

Real updates arrive as a batch. Change-set evidence is being prepared for a limited beta — the outline below is the shape of the work, not something to sign up for today.

Update Change-set Evidence Pack

Preparing a limited beta

STAGE 1

Input

Your current WordPress and PHP versions, a minimal list of active plugins, and the exact version bundle you intend to move to.

STAGE 2

Evidence ledger

Every item graded by where its evidence came from: community, declared metadata, not tested, unknown. The gaps are listed, not smoothed over.

STAGE 3

Phased plan

A bounded decision — PROCEED_WITH_GUARDS, DEFER, INSUFFICIENT_EVIDENCE — with an order to apply things in, preconditions, smoke checks and stop conditions.

No credentials. It never asks for a WordPress login and never reads your orders, customers or database.

No live changes. It does not update, back up or roll back anything. You run the plan.

No guarantee. Rung 4 stays unknown, so a plan can be followed exactly and something can still break.

How a reading is produced

  1. 01 · COLLECT

    Public evidence

    Release history and support threads for the tracked plugins are swept from wordpress.org on a rotation. Only public pages — no credentials anywhere in the process.

  2. 02 · COMPARE

    Against that plugin's baseline

    Threads are attributed to a release, then measured against how much noise that plugin normally generates. Absolute counts mean nothing on their own: a plugin with millions of installs is busier on a quiet day than a small one is on a bad one.

  3. 03 · RETURN

    A bounded reading

    One of five words, the threads behind it, and when the data was collected — so the reasoning can be checked instead of trusted.

Trust boundary. A release check needs no account and no key: you send a plugin slug and a version, and that is the whole input. Site addresses you paste are used to fetch that page and are not kept.

Aggregate call counts are recorded — per day, per tool, per outcome — so the operator can see whether the service is answering anything. Those counters hold no site, no plugin list and no caller identity. The full detail is in the privacy policy.

Questions worth asking first

Is this a security scanner?
No. It reads what other site owners are reporting, which is a different question from whether a release is vulnerable. It is not a CVE lookup and not a malware scan.
Does GUARDED ROLLOUT mean it is safe to update?
No. It means public forum volume for that release looks normal for that plugin, measured the same way for the release and for the ones before it. That is an observation about other people’s sites, not a clearance for yours — plenty of breakage never reaches a forum, and nothing here sees your particular site. Roll it out somewhere low-stakes first.
Can it update my site for me?
No. It changes nothing, anywhere. It has no credentials and no write access by design.
What about premium or custom plugins?
They have no public forum to read, so they cannot be judged here. They are reported as unknown rather than quietly assumed to be fine.
What does NO READ mean?
Not enough has been collected about that plugin yet — a gap on this side, not a finding about the release. It is neither safe nor unsafe.

Check the release you were about to install.

Free, no account. It takes one plugin name and one version number.

Back to the release check