CoderEmbassy Order Vanguard
CoderEmbassy Order Vanguard

CoderEmbassy Order Vanguard

0/5 (0 ratings) — active installs Updated Nov 1, 2026
Screenshot 1

CoderEmbassy Order Vanguard helps WooCommerce stores respond to card testing, bot orders, and repeated fake-checkout attempts.

Protection starts in Monitor mode so store owners can review activity before enabling blocking. The plugin includes:

  • Per-IP, per-email, and store-wide circuit breakers.
  • Store API cart mutation rate limiting and batch inspection.
  • Email, email-domain, and IP blocklists with whitelist precedence.
  • Classic-checkout honeypot protection.
  • Unknown-origin order review signals.
  • A paginated, filterable local Activity Log.
  • Selectable 7, 30, or 90-day activity-log retention with daily batched pruning.
  • Emergency Store API checkout controls with compatibility safeguards.
  • HPOS and WooCommerce Checkout Block compatibility declarations.

Protection data stays in this WordPress site’s database. No external service is required.

Privacy

Order Vanguard stores protection events locally in a custom WordPress database table. Event rows can contain an anonymized or administrator-enabled full IP display value, a one-way site-salted IP hash, request route, event reason, order ID, and bounded technical metadata. Plain-text customer email addresses are excluded from log metadata. Administrators can delete selected rows, select a 7, 30, or 90-day retention period, and choose whether uninstall removes all plugin data.

Source Code and Build

Human-readable admin source and build configuration are included in the plugin package under src/, package.json, and package-lock.json.

The public development repository is:
https://github.com/salehST/coderembassy-order-vanguard

To rebuild the distributed admin assets:

  1. Run npm install from the plugin root.
  2. Run npm run build.

The build uses the WordPress packages listed in package.json and lucide-react, an ISC-licensed icon library. Exact dependency versions and source package URLs are recorded in package-lock.json.