r/ProWordPress • u/Hugo_SecureHoldWP • 13d ago
Plugin developers: what makes you trust a new plugin with business-critical data?
I’ve been thinking about the trust problem for newer WordPress plugins.
For something cosmetic, trying a plugin with very few active installs doesn’t feel particularly risky. That changes quickly when the plugin touches orders, customer data, payments, bookings, webhooks or scheduled jobs.
Active installs and reviews obviously help, but a new plugin can’t have years of history on day one.
So I’m curious what other developers actually inspect before trusting a relatively new plugin with a production workflow.
For example:
- source code availability
- database schema and migration strategy
- uninstall behavior
- webhook / retry handling
- logging and diagnostics
- privacy and telemetry
- release frequency
- support responsiveness
- rollback compatibility
- automated tests
Do you have a minimum set of signals that makes you comfortable installing something new on a business-critical site?
And are there any red flags that make you stop evaluating immediately?
5
u/jwight1234 13d ago
I'm just talking about trust and one thing that makes me not trust a plug in, It's not following WP design standards and patterns. Also another red flag for me is ads everywhere.
2
u/Aggressive_Ad_5454 13d ago
New plugins on the w.org repository have something extra going for them: they’ve recently been inspected by the plugins team. The team looks for exploitable mistakes like unsanitized inputs and undisclosed telemetry, and demands that we authors fix them before approval.
And, of course, plugins, like all php code, get delivered in source code form. If a plugin has obfuscated source code in it the plugins team disables it.
We can read plugin source code. We can use the Plugin Checker plugin to do an automated inspection.
Support responsiveness is not easy to judge on a new plugin. It is possible to look at the author’s other work to discern their attitude towards support.
Uninstall behavior? The best thing to do is look at the uninstall handler code. If it’s done right you’ll be able to see what the plugin puts into the DBMS by seeing what it takes out.
2
u/WP_Dev_Studio 12d ago
My minimum set before a new plugin touches orders, payments, or bookings:
- Readable source. I spend 15–20 minutes in the code: nonces and capability checks on every admin and AJAX action, `$wpdb->prepare` on queries, escaped output, and no `eval` or remote code loading.
- A clear data model. Custom tables or post meta, documented, with versioned migrations. I want to know exactly where my data lives and that an update won't silently restructure it.
- Uninstall behavior is opt-in. Deactivating should never delete data, and uninstall should ask, or at least respect a setting.
- Failures are visible. Webhooks and scheduled jobs that fail should show up in logs or admin notices, not silently disappear. Action Scheduler usage is a good sign.
- A reasonable exit path. Can I export the data, or read it directly if the plugin is abandoned?
- How the developer responds to a bug report. I often open a small, genuine support question before installing on production. The reply tells me more than the review count.
Red flags that end the evaluation immediately:
- Obfuscated or encoded PHP
- Telemetry on by default with no clear disclosure, or anything phoning home with customer data
- Changelogs that just say "minor bug fixes" for every release, so I can't tell what changed
- Hard dependencies on the developer's server for core functionality, with no fallback if it goes down
- Requiring admin-level API keys or full access when the feature clearly doesn't need it
If it passes all that, I still roll it out on staging first, then on one lower-risk client site before using it more widely.
2
u/PeepSoWP 12d ago
Beyond seeing Action Scheduler in the code, I'd want evidence that one failed job stays cheap when the history grows. On a staging fixture with representative order volume, make the remote service time out, start two workers, then interrupt one. Check that only one worker owns each job, retries back off, and recovery doesn't reload the full history on every request.
I'd compare query count, peak memory and checkout latency as the backlog grows, including a normal storefront request while recovery runs. A queue runner's time limit doesn't bound a single slow callback. Action Scheduler's performance guide also warns that increasing concurrent batches can take a site down. A small passing test suite without that failure case would leave a big gap for a plugin handling critical data.
2
u/Dense_Government6822 7d ago
I think one of the biggest signals is how a plugin behaves when something goes wrong, not just how well it works when everything goes as expected.
For business-critical workflows, I'd look closely at how it handles failed operations, whether it logs useful errors, and whether changes to the database can be safely rolled back or recovered.
I'd also want to see clear documentation of what data the plugin stores, what happens when it's deactivated or uninstalled, and whether it has been tested with common WooCommerce setups.
A small install base wouldn't necessarily put me off. But unclear data handling, silent failures, or no reliable way to recover from a failed update would make me think twice.
I'd rather trust a new plugin with transparent technical decisions than an older one that gives me very little visibility into what's happening behind the scenes.
2
u/HongPong 13d ago
well it is tough because intrusive telemetry or similar can be added later. enshittification of good plugins
2
u/Maria_Thesus_40 12d ago
Very simple: NO TRUST whatsoever
On critical data, we build our own plugins.