--- type: Decision title: Vulnerability audit policy description: The dependency audit blocks the pipeline, with an explicit reviewed ignore-list for advisories that have no patched release - the list lives in pnpm-workspace.yaml, because pnpm 11 no longer reads the pnpm field in package.json. tags: [decision, security, ci, audit, pnpm] status: draft generated: { by: opencode-go/glm-5.3-flash, at: 2026-10-18T19:10:00Z } verified: { by: human:noel, at: not yet } sources: - id: workspace resource: pnpm-workspace.yaml title: auditConfig.ignoreGhsas - id: audit-job resource: .gitea/workflows/pr-checker.yml title: Dependency audit job --- # Decision `pnpm audit --prod --audit-level moderate` stays **blocking** (no `continue-on-error`). Advisories that cannot be fixed by upgrading are not silenced but **reviewed and recorded**: `auditConfig.ignoreGhsas` in `pnpm-workspace.yaml`, each entry with the date and reason, removed when a patched version ships. Advisories that DO have a patch take the upgrade route: the patched version is forced with `overrides` in `pnpm-workspace.yaml`. First use (2026-10-20): `postcss-selector-parser: 7.1.6` over the `6.1.4` that `tailwindcss` 3.4.19 pins via `postcss-nested` 6.2.0 (GHSA-rj75-hqrm-r3gf, moderate) - the patched 7.1.6 was already in the tree via `postcss-nesting` and proved API-compatible through a full build. The override is removed when `tailwindcss` ships `>= 7.1.6` itself or the site moves to Tailwind v4. Currently ignored (verified against the advisory database and the npm registries on 2026-10-31): * `GHSA-vfj7-8cjw-p6xm` - braces <= 3.0.3, high. Path: `nitropack > globby > micromatch > braces` - globbing during build, no attacker-controlled patterns at runtime. * `GHSA-g3hv-75wg-m249` - minimatch < 11.0.1, moderate. The patch (11.0.1) dropped the `makeRe` export that `eslint-plugin-import-x` imports, so forcing it breaks `pnpm lint` with "does not provide an export named 'makeRe'"; it also breaks ESLint's config loader. All affected paths are build/lint-time (Nitro, i18n, ESLint via vite-plugin-checker), never in the running server. The 2026-10-31 round also upgraded `nuxt` 4.6.2 -> 4.6.3 (fixes the Nuxt dot-segment, dev-server and appSecret advisories) and added overrides for `node-forge: 1.4.1` (the old node-forge ignore, `GHSA-86w9-cpqp-85rv`, is gone - a patch now exists) and `glob: 14.0.2` for `GHSA-3g3m-2fjr-6pw4` (scoped to `>=9.0.0 <=14.0.1` so tailwind-config-viewer keeps glob 7). # Why A red job that can never go green trains everyone to ignore red - the same silent-failure outcome "nothing fails silently" exists to prevent. The ignore list is the opposite of silence: the audit still names what it skipped ("1 ignored: 1 high") and the decision lives in a reviewable file. # The pnpm 11 lesson The first attempt put `auditConfig` under the `pnpm` field in `package.json`. pnpm 11 warned and **ignored it** - settings moved to `pnpm-workspace.yaml` (same reason the config-only workspace file needed pnpm 11 in the first place). The warning was caught locally before pushing by running the exact CI command. # Revisit when * A patched version ships for either package - remove the entry. * A new advisory appears with a real patch - fix it by upgrading; the audit gate does the enforcement. * Snyk is re-enabled (its SAST/DAST scope is different; see [snyk-paused-and-secrets-policy](snyk-paused-and-secrets-policy.md)).