Milestones

List view

• v2.3.2 — safe on a stranger's site

  The plugin is live on wordpress.org as 2.3.1 (153 downloads, 0 ratings, 0 support threads) and is not yet safe to run unattended on a site behind a CDN or reverse proxy. Every issue here is verified by direct code reading against the shipped tag, with the mitigations and non-firing conditions stated. Ships as 2.3.2.

  No due date

  •14/14 issues closed
  100% complete0 open14 closed

• Cloud monetization P1

  Plugin side: feed sync + network blocking, intel column, post-CRITICAL moment, Upgrade checkout wiring. Ships as 2.4.0.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Cloud monetization P0

  Plugin side of prds/wordpress-monetization.md (app repo): one-click connect, digest consent, entitlements sync

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• v2.2 — Node SDK parity & deception enforcement

  Bring the WordPress plugin to capability parity with @webdecoy/node 0.4.x — rules engine (rate-limit/filter/tripwire), honeytokens, violation batch reporting, IP enrichment, stealth (F1) detection, and the wd_clearance loop (WebDecoy/app#124/#128/#136 named the WP surface as follow-on) — then go beyond parity with deception only server-side PHP can do: fake decoy content with canary credentials, WP-native traps (XML-RPC, user enumeration, fake vulnerable-plugin paths), and WooCommerce honeytoken coupons.

  No due date

  •16/16 issues closed
  100% complete0 open16 closed