From 76650abd32ff940890f4a29dd3a0ce687d900830 Mon Sep 17 00:00:00 2001
From: Tang Rufus <tangrufus@gmail.com>
Date: Fri, 24 Jul 2026 23:22:12 +0100
Subject: [PATCH] Update `config.audit` to `config.policy`

To adopt the new schema introduced since Composer v2.10.0:

- https://github.com/composer/composer/issues/12786
- https://github.com/composer/composer/pull/12804
---
 ...diting-wordpress-vulnerabilities-with-composer.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/bedrock/auditing-wordpress-vulnerabilities-with-composer.md b/bedrock/auditing-wordpress-vulnerabilities-with-composer.md
index fb88acdd..cd8c3717 100644
--- a/bedrock/auditing-wordpress-vulnerabilities-with-composer.md
+++ b/bedrock/auditing-wordpress-vulnerabilities-with-composer.md
@@ -1,10 +1,11 @@
 ---
-date_modified: 2026-05-03 12:00
+date_modified: 2026-07-24 23:00
 date_published: 2026-05-03 12:00
 description: Audit WordPress plugins and themes for known vulnerabilities with Composer using WP Sec Adv, a security advisory repository sourced from Wordfence Intelligence.
 title: Auditing WordPress Vulnerabilities with Composer
 authors:
   - ben
+  - tangrufus
 ---
 
 # Auditing WordPress Vulnerabilities with Composer
@@ -45,11 +46,10 @@ Not every advisory requires immediate action. Composer lets you acknowledge spec
 ```json
 {
   "config": {
-    "audit": {
-      "ignore": {
-        "CVE-2026-3589": {
-          "apply": "block",
-          "reason": "Waiting for upstream fix in v1.2.3. Allow during updates but still report in audits"
+    "policy": {
+      "advisories": {
+        "ignore-id": {
+          "CVE-2026-3589": "Waiting for upstream fix in v1.2.3. Allow during updates but still report in audits"
         }
       }
     }