? Verifying lockfile against supply-chain policies (327 entries)... ✗ Lockfile failed supply-chain policy check (327 entries in 1.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 32 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.66.0 was published at 2026-05-19T08:07:03.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-android-arm64@1.66.0 was published at 2026-05-19T08:06:33.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-darwin-arm64@1.66.0 was published at 2026-05-19T08:06:27.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-darwin-x64@1.66.0 was published at 2026-05-19T08:07:50.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-freebsd-x64@1.66.0 was published at 2026-05-19T08:08:01.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-arm-gnueabihf@1.66.0 was published at 2026-05-19T08:07:08.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-arm-musleabihf@1.66.0 was published at 2026-05-19T08:07:13.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-arm64-gnu@1.66.0 was published at 2026-05-19T08:06:46.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-arm64-musl@1.66.0 was published at 2026-05-19T08:06:52.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-ppc64-gnu@1.66.0 was published at 2026-05-19T08:07:25.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-riscv64-gnu@1.66.0 was published at 2026-05-19T08:07:31.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-riscv64-musl@1.66.0 was published at 2026-05-19T08:07:36.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-s390x-gnu@1.66.0 was published at 2026-05-19T08:07:44.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-x64-gnu@1.66.0 was published at 2026-05-19T08:08:08.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-linux-x64-musl@1.66.0 was published at 2026-05-19T08:08:14.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-openharmony-arm64@1.66.0 was published at 2026-05-19T08:06:58.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-win32-arm64-msvc@1.66.0 was published at 2026-05-19T08:06:40.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-win32-ia32-msvc@1.66.0 was published at 2026-05-19T08:07:19.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @oxlint/binding-win32-x64-msvc@1.66.0 was published at 2026-05-19T08:07:55.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) @vizejs/native-darwin-arm64@0.108.0 was published at 2026-05-19T09:39:34.000Z, within the minimumReleaseAge cutoff (2026-05-18T11:46:50.363Z) …and 12 more The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.