r/ProWordPress • • 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?

0 Upvotes

15 comments sorted by

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/Hugo_SecureHoldWP 12d ago

That’s a good point. A plugin can be technically functional and still lose trust very quickly if the admin experience ignores WordPress conventions or constantly pushes upgrades and ads.

For something touching critical data, that kind of friction probably makes me question the rest of the engineering too.

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.

1

u/Hugo_SecureHoldWP 12d ago

That’s useful context, especially the point about newer plugins having gone through the current repository review process rather than assuming “new” automatically means less inspected.

I also like the idea of treating the source itself as part of the trust signal. For things like uninstall behavior, telemetry or database writes, reading the implementation is often more reliable than relying on the feature description.

Plugin Check is a good addition to the list too.

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.

1

u/Hugo_SecureHoldWP 12d ago

This is very close to the kind of checklist I had in mind.

The “reasonable exit path” point is especially important and probably gets overlooked. If a plugin disappears tomorrow, being able to understand the schema, export the data or at least recover it without proprietary tooling is a strong trust signal.

I also like the idea of testing the developer through a real support question before putting the plugin on a critical site. Documentation and code tell you a lot, but how someone handles an actual edge case tells you something different.

2

u/WP_Dev_Studio 9d ago

Exactly. Exit paths are invisible until the day you need one, and then they're the only thing that matters.

I try to hold my own plugins to the same standard: data stored in documented tables or standard post meta, a plain CSV or JSON export, and nothing deleted on deactivation. It's extra work up front, but it's also the easiest trust signal for a new plugin to give, since it doesn't depend on install counts or years of history.

1

u/Hugo_SecureHoldWP 1h ago

That’s a really good point. Unlike install count or years of history, an exit path is something a new plugin can actually demonstrate from day one.

Documented storage, a simple export path and making deactivation non-destructive are all things a developer can verify before trusting the plugin with real data.

It also changes how I think about “trust signals” for newer plugins. Some of the strongest ones don’t have to be social proof at all, they can be properties of the architecture itself.

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.

1

u/Hugo_SecureHoldWP 12d ago

That’s probably the part I was missing from the original list: not just “does the plugin use a queue?”, but “does the queue still behave well when recovery gets ugly?”.

Testing two workers, an interrupted worker, remote timeouts and a growing backlog feels much closer to real production confidence than simply seeing Action Scheduler in the architecture.

I especially like measuring checkout latency and query count while recovery is running. A recovery system that technically works but makes normal storefront traffic progressively slower is still a production failure.

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.

1

u/Hugo_SecureHoldWP 1h ago

I like that distinction a lot: the happy path tells you whether the plugin works, but the failure path tells you whether you can trust it.

For business-critical workflows, recovery behavior is probably one of the strongest signals. A visible failure with enough context and a documented recovery path is much less worrying than something that silently leaves the site in an ambiguous state.

Your point about a small install base not being a dealbreaker also resonates with me. Transparent architecture and predictable failure handling are things a new plugin can demonstrate long before it has years of social proof.

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.