WordPress Plugin Release & Compatibility Risk Monitor

Monitor public WordPress.org plugin metadata for releases, requirement changes, tested-up-to lag, stale maintenance signals, and directory availability.

Unofficial community tool. This Actor is not affiliated with, endorsed by, or sponsored by WordPress.org, the WordPress Foundation, Automattic, or any plugin vendor.

Buyer value

Agencies, plugin vendors, managed hosts, and maintenance teams can schedule this Actor to turn a plugin watchlist into structured snapshots and deterministic changes. It uses the official public WordPress.org Plugin Information API—no site credentials, admin access, or arbitrary crawling.

Quick start

1. Click Try for free and paste the input below.
2. Run it once to create a baseline for the watchlist.
3. Schedule the same input daily or weekly. Later runs emit typed changes against the last fully successful baseline.
4. Download REPORT.html from the run's key-value store for a prioritized, print-to-PDF pre-flight report, or route structured dataset rows into the maintenance queue.

{
  "pluginSlugs": ["woocommerce", "wordfence"],
  "currentWordPressVersion": "6.8",
  "staleAfterDays": 365,
  "useStoredState": true
}

Start with two plugins to validate the output. A 25-plugin watchlist costs $0.05 in Actor charges at the current price, plus Apify platform usage.

Need a client-ready review?

If you need a human-reviewed handoff rather than raw monitoring output, request the WordPress Plugin Upgrade Risk Audit: €149 prepaid, covering up to 25 public WordPress.org plugins with delivery within two business days after valid intake and confirmed payment.

Request the €149 audit

Send only the public plugin slugs, target WordPress version, and non-sensitive context. Do not send site credentials, private plugin files, customer data, or production access. The audit uses public directory metadata, prioritizes upgrade-review signals, and does not replace staging, backups, vulnerability scanning, or vendor guidance.

Output

One plugin_snapshot per successful lookup, a plugin_fetch_error for unavailable/API-failed slugs, and a final summary. Snapshots include versions, WordPress/PHP requirements, tested-up-to, last update, active installs, typed changes, deterministic risk signals, and source URLs.

Every run also writes REPORT.html to the default key-value store. It is a self-contained, print-friendly report sorted high-risk first, with no external scripts, styles, or tracking requests. Use it as a staging-review handoff; it retains the same public-metadata limitations as the dataset.

Comparison

By default the Actor stores the last fully successful snapshot set in a named Apify key-value store. Independent slug sets receive separate stable record keys. You can instead supply previousSnapshots; explicit snapshots—including an explicit empty array—take precedence.

Risk semantics

• tested_up_to_lag: target WordPress version exceeds the directory's tested-up-to value.
• stale_release: directory update is older than your threshold.
• major_version_change: the numeric major version increased.
• requiresWordPress_increased / requiresPhp_increased: minimum runtime requirement increased.

These are upgrade-review signals, not vulnerability findings, compatibility guarantees, or legal/security advice. WordPress.org metadata can be delayed, incomplete, or changed by maintainers. Test upgrades on staging and consult the plugin vendor.

Billing

The current price is $0.002 per attempted plugin lookup ($2.00 per 1,000). For example, a 25-plugin watchlist costs $0.05 in Actor charges per run, plus Apify platform usage.

The pay-per-event event is plugin-lookup-attempted, charged immediately before each official API lookup. A lookup that later fails can therefore be billable, but emits a visible plugin_fetch_error record. Processing stops cleanly if the spending cap rejects the next event. Dataset items are not charged again.

Privacy

The Actor accepts WordPress.org directory slugs plus optional comparison/state settings, calls only the fixed official api.wordpress.org endpoint, and needs no credentials or site/customer data. See PRIVACY.md.