ci: ban arrayref 0.3.10 and proc-macro1

.github/workflows/ci.yml

@@ -46,7 +46,23 @@ jobs:
         uses: actions/checkout@v5
 
       - name: Check feature ${{ matrix.feature }}
-        run: cargo check --no-default-features --features ${{ matrix.feature }}
+        run: cargo check --locked --no-default-features --features ${{ matrix.feature }}
+
+  cargo_deny:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Harden runner
+        uses: step-security/harden-runner@05e31511f85b41b11d1cf0ef85d0992719546e2c # v2.21.0
+        with:
+          egress-policy: audit
+
+      - name: Clone repository
+        uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5.1.0
+
+      - name: Check bans
+        uses: EmbarkStudios/cargo-deny-action@3c6349835b2b7b196a839186cb8b78e02f7b5f25 # v2.1.1
+        with:
+          command: check bans
 
   toml_format:
     runs-on: ubuntu-latest

deny.toml

@@ -0,0 +1,11 @@
+# arrayref 0.3.10 was published from a compromised owner account and pulls in
+# proc-macro1, a typosquat of proc-macro2 whose build script downloads and
+# executes a remote binary. All earlier arrayref releases were yanked to
+# pressure consumers into updating to the malicious version. arrayref reaches
+# this tree via blake3; keep it pinned at the version in Cargo.lock and do not
+# update past these bans until crates.io removes the malicious release.
+[bans]
+deny = [
+  { crate = "arrayref@0.3.10", reason = "malicious release from compromised owner account" },
+  { crate = "proc-macro1", reason = "typosquat of proc-macro2; build script executes a remote binary" },
+]