Update Compass

Update Compass is a decision-first WordPress admin plugin that helps you evaluate plugin and theme updates before installing them.

Instead of only showing that an update is available, Update Compass adds a local analysis layer and recommends what to do next based on version changes, compatibility metadata, changelog signals, and release timing.

It keeps the native WordPress update workflow. Updates are still performed through standard WordPress update mechanisms.

How It Works

WordPress already detects updates. Update Compass reads that data and adds decision guidance such as:

• Update Ready
• Stage & Test
• Watch & Wait
• Hold Off
• Needs Review

Each status includes a short explanation and next-step guidance. For higher-risk updates, users can open status details for deeper analysis and reminder scheduling.

Key Features

• Pre-update risk analysis for plugins and themes
• Clear status badges with explanations and next steps
• Version jump analysis (major, minor, patch deltas)
• WordPress compatibility checks (requires / tested)
• Changelog keyword detection (best effort)
• Changelog links (WordPress.org modal/external links when available)
• Reminder dates for monitoring and re-check workflows
• Bulk update selection with caution confirmation for non-ready updates
• Local-first workflow, no external account required

Who Is This For

• WordPress developers
• Agencies maintaining multiple sites
• Site owners managing complex plugin/theme stacks
• WooCommerce or multilingual sites where update risk is higher

Decision Logic (Summary)

Update Compass uses local rules to assess update risk, including:

• Version delta analysis (major/minor/patch jumps)
• WordPress compatibility metadata checks
• Changelog keyword signals (when changelog text is available)
• Release recency and stale-project checks
• Changelog availability (flags manual review when missing)

External Services

Update Compass is local-first and does not require an account.

To improve changelog-based reasoning, it may make server-side requests to publicly available changelog/metadata endpoints when available (for example WordPress.org plugin/theme metadata and changelog pages, or vendor-provided changelog URLs exposed in WordPress update data).

This is best-effort only and used to enrich analysis. Core update detection still relies on WordPress native update transients.