? Verifying lockfile against supply-chain policies (333 entries)... ✗ Lockfile failed supply-chain policy check (333 entries in 2.1s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 11 lockfile entries failed verification: @voidzero-dev/vite-plus-core@0.1.23 was published at 2026-05-29T02:58:30.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-darwin-arm64@0.1.23 was published at 2026-05-29T02:56:36.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-darwin-x64@0.1.23 was published at 2026-05-29T02:56:46.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-linux-arm64-gnu@0.1.23 was published at 2026-05-29T02:56:54.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-linux-arm64-musl@0.1.23 was published at 2026-05-29T02:57:02.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-linux-x64-gnu@0.1.23 was published at 2026-05-29T02:57:10.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-linux-x64-musl@0.1.23 was published at 2026-05-29T02:57:18.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-test@0.1.23 was published at 2026-05-29T02:58:36.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-win32-arm64-msvc@0.1.23 was published at 2026-05-29T02:57:25.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) @voidzero-dev/vite-plus-win32-x64-msvc@0.1.23 was published at 2026-05-29T02:57:33.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) vite-plus@0.1.23 was published at 2026-05-29T02:58:41.000Z, within the minimumReleaseAge cutoff (2026-05-28T05:45:26.403Z) 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.