pnpm-workspace.yaml

# Register .claude/hooks/* as workspace packages so taze (run via
# `pnpm run update`) sees and bumps their package.json manifests
# alongside the root. Keeps hook deps in lockstep with the main tree.
#
# tools/* — developer-only utilities (audit/codemod scripts). Not
# published, not part of the dist tree.
packages:
  - .config/fleet/oxlint-plugin
  - .config/fleet/oxlint-plugin/fleet/*
  - .config/repo/oxlint-plugin/*
  - tools/*
  - '.claude/hooks/fleet/*'
  - '.claude/hooks/repo/*'
enableGlobalVirtualStore: true
  # vite 8.1.0 — dev dep (vitest's bundler). 8.1 adds experimental.bundledDev
  # (NOT adopted — experimental, and the fleet runs stable-only). Published
  # within the 7-day soak; exact-pinned so a future 8.1.1 still soaks.
  # taze 19.16.0 — the dep updater itself; forced ahead of the soak by owner
  # directive so the regenerated single-registry patch (patchedDependencies)
  # tracks the current release. Exact-pinned so a future version re-soaks.
  # shadscan 0.2.0 — deterministic UI audits for shadcn apps, used by the
  # design skills; forced ahead of the soak by owner directive. Exact-pinned
  # so a future version re-soaks.
  # verkit — new dev-only transitive of taze 19.16.0 (same owner directive);
  # exact-pinned so future versions re-soak.
  # js-yaml 5.2.2 — HIGH security fix, GHSA-pm4m-ph32-ghv5: exponential parse
  # time in flow collections. The canonical overrides entry forces it past
  # markdownlint-cli2 0.23.1's vulnerable 5.2.1 exact-pin. Soak bypassed per
  # the high-severity security exception; exact-pinned so a future version
  # re-soaks.
catalog:
  # agent-ci runs a repo's GitHub Actions workflows locally in Docker so a
  # change can be validated before it's pushed (see the `agent-ci` skill).
  # The published package is a self-contained Node CLI (`dist/cli.js`) — no
  # platform-binary optionalDependencies, despite the monorepo's internal
  # workspace layout. dtu-github-actions is its GitHub-Actions parser, pinned
  # explicitly (not left transitive) so its version is uniform fleet-wide.
  '@redwoodjs/agent-ci': 0.17.1
  '@ultrathink/acorn.rs.wasm': 0.1.1
  'brace-expansion': 5.0.9
  'dtu-github-actions': 0.17.1
  # shadscan — shadcn UI audit CLI for the design skills (missing UI
  # fundamentals report). Exact-pinned; the whole package is younger than
  # the soak window, so it carries a minimumReleaseAgeExclude entry below.
  '@shadscan/cli': 0.11.0
  '@sinclair/typebox': 0.34.52
  'ecc-agentshield': 1.4.0
  # typebox 1.x — the unscoped rewrite of @sinclair/typebox. Both names are
  # pinned while the fleet migrates; the 0.x entry is deleted once no member
  # imports the scoped name. 1.3.10 is inside the 7-day soak, so it carries a
  # dated minimumReleaseAgeExclude entry above.
  'typebox': 1.3.11
  '@socketregistry/packageurl-js': 1.5.2
  # -stable aliases: pnpm `overrides:` can't redirect a package's own
  # name when used INSIDE that same package — Node ESM treats it as a
  # self-reference and resolves through the local exports map, not
  # the override. The 4 Socket-published packages therefore need a
  # SECOND name (`<canonical>-stable`) aliased via `npm:` to the
  # published version. Build / hook / script / config code uses the
  # -stable name so it always resolves to the published catalog
  # version regardless of where the importing file lives. src/ +
  # test/ code uses the canonical name because vitest aliases that
  # to local src/.
  '@socketregistry/packageurl-js-stable': 'npm:@socketregistry/packageurl-js@1.5.2'
  '@socketsecurity/lib': 6.7.0
  '@socketsecurity/lib-stable': 'npm:@socketsecurity/lib@6.7.0'
  '@socketsecurity/registry': 2.0.5
  '@socketsecurity/registry-stable': 'npm:@socketsecurity/registry@2.0.5'
  '@socketsecurity/sdk': 4.1.4
  '@socketsecurity/sdk-stable': 'npm:@socketsecurity/sdk@4.1.4'
  '@types/mdast': 4.0.4
  '@types/node': 26.2.0
  '@types/semver': 7.8.0
  '@types/shell-quote': 1.7.5
  'compromise': 14.16.0
  # fast-check — property-based testing for pure fleet-script logic (pin
  # derivation, version compare, config validation). Runs standalone in vitest.
  # published: 2026-07-08 (past 7-day soak). See .claude/skills/fleet/property-testing.
  'fast-check': 4.9.0
  'magic-string': 1.1.0
  'markdownlint-cli2': 0.23.2
  'mdast-util-from-markdown': 2.0.3
  # GFM pair for render-faithful markdown parsing (tables, footnotes,
  # strikethrough, autolinks) — mdast-util-from-markdown must always be
  # combined with micromark-extension-gfm + mdast-util-gfm.
  'mdast-util-gfm': 3.1.0
  # The serializer half, for tools that legitimately EMIT markdown; edits to
  # existing documents stay position-based (never a whole-doc round-trip).
  'mdast-util-to-markdown': 2.1.2
  'micromark': 4.0.2
  'micromark-extension-gfm': 3.0.0
  'minimatch': 10.2.6
  'neosanitize': 0.3.0
  # nock — HTTP mocking for tests (disableNetConnect() + stubs). Pinned back
  # from the @mswjs/interceptors rewrite: npm deprecates 15.0.0 ("released
  # accidentally"), so the catalog-drift automation skips it and this pin is
  # hand-aligned with the canonical fleet catalog; bump to the stabilized 15.x
  # when it ships.
  'nock': 14.0.17
  # npm-high-impact 1.13.0 — wooorm's high-impact npm package lists
  # (npmHighImpact + npmTopDependents + npmTopDownloads); the ecosystem-reach
  # input for scripts/fleet/measure-ecosystem-impact.mts, which ranks override
  # candidates before simulating what a port actually cuts. Published
  # 2026-06-08, past the 7-day soak.
  'npm-high-impact': 1.13.0
  'oxfmt': 0.62.0
  'oxlint': 1.77.0
  'oxlint-tsgolint': 7.0.2001
  # parse5 — the HTML parser half of the markdown story. mdast hands raw HTML
  # back as an opaque `html` node (README `<picture>`/`<img>` blocks), so
  # attribute-level edits need parse5's per-attribute source locations to land
  # on a real attribute value instead of a string match. Paired with the mdast
  # + micromark GFM entries above; see lib/markdown-ast.mts.
  'parse5': 8.0.1
  # playwright-core — headless Chromium driver for the seeing-rendered-output
  # skill (render a page / unpacked MV3 extension popup to PNG). Fleet-canonical
  # catalog dep; source of truth is template/pnpm-workspace.fleet.yaml.
  'playwright-core': 1.62.1
  # portless — stable HTTPS `.localhost` URLs for local page tests and rendered UI checks.
  'portless': 0.15.5
  # Direct bundler pin for repos that run rolldown as their build
  # (socket-packageurl-js, socket-webext, the trusted-publisher
  # extension, and the in-progress esbuild→rolldown migrations).
  # Single-sourcing the version here stops the per-repo drift
  # (was 1.0.0 / 1.0.1 / 1.0.2 across adopters). Matches the
  # vite-bundled rolldown (8.0.14 → 1.0.2); the per-platform
  # @rolldown/binding-* + @oxc-project/types stay as soak-excluded
  # transitives (consumers depend on `rolldown` only).
  'regjsparser': 0.13.2
  'rolldown': 1.2.3
  'semver': 7.8.5
  'shell-quote': 1.10.0
  'taze': 20.0.0
  # vite 8.0.16 swaps esbuild → rolldown natively (bundles rolldown
  # 1.0.2) and patches the <=8.0.15 advisories (GHSA-fx2h-pf6j-xcff
  # high, GHSA-v6wh-96g9-6wx3 medium). Tracked here so the pnpm
  # override below pins every transitive `vite` (vitest, @vitest/*,
  # plugin authors) to it.
  'typescript': 7.0.2
  'vitest': 4.1.10
  '@vitest/coverage-v8': 4.1.10
  c8: 12.0.0
  'chrome-devtools-mcp': 1.6.0
  # Playwright MCP server — agent-driven browsing with the fleet agent-banner
  # init script (see .config/fleet/playwright/).
  '@playwright/mcp': 0.0.79
  '@vitest/ui': 4.1.10
  # Alias to the post-rename artifact at the version this repo already
  # installs (dedup: one acorn.rs.wasm major); the pre-rename
  # @ultrathink/acorn-wasm name is npm-deprecated.
  '@vitiate/core': 0.3.1
  '@typescript/native-preview': 7.0.0-dev.20260510.1
  'html5parser': 3.0.0
  'npm-run-all2': 9.0.3
  # Source of truth for CI-provider + AI-agent env-var detection. devDep only:
  # the build-time codemod inlines its isCI/isAgent boolean expressions into
  # dist, so it never enters the runtime dependency tree. Published 2026-04-15,
  # well past the 7-day soak — no minimumReleaseAgeExclude needed.
  'std-env': 4.2.0
  'svgo': 4.0.2
  # Test-only tar extraction seam for archives coverage; single-sourced here so
  # the devDep and the dedup override below stay on one pin.
  'tar-fs': 3.1.3
  'vite': 8.2.0
  'vitiate': 0.3.1

# Native post-install build scripts. These three arrive transitively via
# @redwoodjs/agent-ci's `ssh2` (optional crypto acceleration). agent-ci's
# published CLI (`dist/cli.js`) runs without them — verified `agent-ci --help`
# works with the builds skipped — so we decline to run their post-install
# scripts. Declining is the safe default; running native build scripts from a
# transitive dep is unnecessary attack surface here.
allowBuilds:
  # Optional native addon for ssh2 crypto acceleration; JS fallback is fine.
  cpu-features: false
  # Ships prebuilt dist; its postinstall codegen isn't needed as a dependency.
  protobufjs: false
  # Fleet browser automation is playwright-core (page + extension-popup PNG) and
  # chrome-devtools-mcp; puppeteer itself is unused. Kept as a guard — no dep
  # pulls puppeteer today, but if a transitive ever does, its Chrome-download
  # postinstall stays declined (playwright-core already supplies the browser).
  puppeteer: false
  # Native bindings are optional (cpu-features above); pure-JS paths suffice.
  ssh2: false
  # The published sdk leaks fleet repo scripts including a preinstall
  # (bootstrap-zero-dep-packages.mjs) meant for the sdk repo itself, not
  # consumers. Explicitly deny it.
  '@socketsecurity/sdk': false
  '@swc/core': true
  esbuild: true
  rolldown: true

# Soak time for external-tools updates: minutes a release must have
# existed before scripts/fleet/external-tools/update.mts will consider it
# (mirrors pnpm's `minimumReleaseAge` for npm catalog entries). 10080
# minutes = 7 days. Same value fleet repos use.
minimumReleaseAge: 10080
minimumReleaseAgeExclude:
  # Socket-owned scopes — bypass the soak window because they ship
  # through Socket's own provenance + publish pipeline. Canonical
  # list: scripts/constants/socket-scopes.mts SOCKET_PACKAGE_PATTERNS.
  # Mirrored in `.config/taze.config.mts` (same scopes, same reason)
  # and consumed by scripts/fleet/external-tools/update.mts via
  # isSocketSourcedPackage / isSocketSourcedRepository.
  - '@socketoverride/*'
  - '@socketregistry/*'
  - '@socketsecurity/*'
  - 'sfw'
  - 'socket'
  # pnpm and the other external tools are NOT listed here. Their soak bypass
  # lives inline in scripts/fleet/setup/external-tools.json as a per-tool
  # `soakBypass` block carrying `published` + `removable` dates, which
  # `soak-exclude-scope-guard` requires (this list is Socket-owned scopes only)
  # and which auto-disarms on the `removable` date instead of lingering here.
  # Agent-CI 0.17.1 gives each job private writable node_modules and shares
  # completed pnpm/Yarn/Bun dependency trees through atomic lockfile-keyed
  # snapshots. dtu-github-actions is its matching workflow-parser package.
  # Both are dev-only local-CI tools and must stay on the same exact version.
  # playwright-core@1.55.1 — headless Chromium driver for the
  # rendering-chromium-to-png skill. Well-known Microsoft package, dev-only
  # (renders PNGs an agent can read; no runtime/ship surface). Long past soak;
  # listed for cascade parity. Exact-pinned so a future minor re-soaks.
  # compromise@14.15.1 is the attested re-publish that clears the
  # trust-downgrade flag on 14.15.0. The catalog bump to 14.15.1 + the
  # removed `trustPolicyExclude: compromise@14.15.0` need a matching
  # lockfile entry, and 14.15.1 published today so the resolution needs
  # a soak bypass. Scoped to the exact tag so a future 14.15.2 still
  # goes through the normal soak time.
  # vite 8.0.14 ships rolldown 1.0.2 natively (no esbuild transitive).
  # Excluded from the 7-day soak so we can pull the rolldown-based
  # build now — the fleet rule "bundler = rolldown, not esbuild"
  # trumps the soak heuristic for this one pinned version. Scoped to
  - '@stuie/*'
  - '@ultrathink/*'
  # oxfmt 0.55.0 — the formatter; bumped from 0.48.0 for its jsdoc fixes.
  # The main package + per-platform binding family are pinned to the exact
  # version (a scope glob would blanket-bypass any future @oxfmt publish). All
  # published within the 7-day soak; exact-pinned so a future 0.56 re-soaks.
  # oxlint 1.75.0 — the linter; catalog-pinned at 1.75.0. The main package + its
  # per-platform binding family are soak-excluded because oxlint is a
  # known-publisher (oxc) tool and the fleet MIGRATES + SUPPORTS its plugin API
  # (the socket/* rules are kept current with oxlint's plugin surface), so a
  # fresh oxlint is adopted immediately rather than pinned back. The soak targets
  # npm freshpub typosquats, not a first-party oxc release.
  - '@sdxgen/*'
  - 'sdxgen'

# Refuse transitive (sub-) deps declared via git/tarball/local-tarball
# specs. Direct git deps in this repo are still allowed; this only
# affects what nested dependencies are permitted. Defends against a
# package listing a git URL in its own dependencies — a supply-chain
# vector that bypasses npm registry validation. pnpm's current
# default is `false`; declared explicitly so a future default flip
# can't silently widen the trust boundary.
blockExoticSubdeps: true

# Proceed with a node_modules purge WITHOUT an interactive confirm. The fleet
# runs pnpm non-interactively everywhere (skills, scripts, hooks, agents, CI) —
# no TTY. pnpm's default ABORTS a purge for lack of a TTY
# (ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY), wedging any commit whose
# pre-commit re-checks deps after a workspace/.npmrc change. Purging
# node_modules is safe (gitignored + regenerable). Unlike CI=true this does NOT
# force a frozen lockfile; CI keeps owning frozen-vs-update policy.
confirmModulesPurge: false

# pnpm `overrides` block — two purposes:
#
# 1. Force every transitive `vite` resolution to the catalog'd 8.0.13.
#    Vitest 4.1.6 advertises support for `vite: ^6.0.0 || ^7.0.0 || ^8.0.0`,
#    so the bump is compatible. The override is what actually removes
#    esbuild from the install tree — without it, vitest would still
#    resolve vite ^6.x.
#
# 2. Force every consumer of Socket's own packages to resolve through
#    the catalog-pinned published versions. The `catalog:` form rewrites
#    `workspace:*`, `^x.y.z`, and bare-version specs alike to the version
#    in the default `catalog:` block above. This is the safety property
#    that prevents accidental local-checkout resolution when a sibling
#    repo is on disk: even if a downstream package declares
#    `"@socketsecurity/lib": "workspace:*"`, pnpm rewrites it to the
#    pinned npm version instead of a sibling working tree.
overrides:
  # Fleet-canonical overrides (managed by socket-wheelhouse sync; do not edit).
  '@sinclair/typebox': 'catalog:'
  '@socketregistry/packageurl-js': 'catalog:'
  '@socketsecurity/lib': 'catalog:'
  '@socketsecurity/registry': 'catalog:'
  '@socketsecurity/sdk': 'catalog:'
  'brace-expansion@>=4': '5.0.9'
  'chalk@>=5': '5.6.2'
  'es-define-property': 'npm:@socketregistry/es-define-property@1.0.7'
  'es-set-tostringtag': 'npm:@socketregistry/es-set-tostringtag@1.0.10'
  'function-bind': 'npm:@socketregistry/function-bind@1.0.7'
  'glob': '13.0.6'
  'gopd': 'npm:@socketregistry/gopd@1.0.7'
  'has-symbols': 'npm:@socketregistry/has-symbols@1.0.7'
  'has-tostringtag': 'npm:@socketregistry/has-tostringtag@1.0.7'
  'hasown': 'npm:@socketregistry/hasown@1.0.7'
  'iconv-lite': '0.7.3'
  'isexe@>=3': '4.0.0'
  'js-yaml@>=5.0.0 <5.2.2': '5.2.2'
  'lru-cache@>=10': '11.5.2'
  'magic-string': '1.1.0'
  'mime-db': '1.54.0'
  'mime-types@>=3': '3.0.2'
  'minimatch@>=3': '10.2.6'
  'minipass@>=4': '7.1.3'
  'postcss@>=8': '8.5.25'
  'safe-buffer': 'npm:@socketregistry/safe-buffer@1.0.9'
  'safer-buffer': 'npm:@socketregistry/safer-buffer@1.0.10'
  'semver@>=5.0.0 <7.6.0': '7.8.5'
  'side-channel': 'npm:@socketregistry/side-channel@1.0.10'
  'ssri@>=12': '13.0.1'
  'string-width@>=5': '8.2.2'
  'tinyexec': '1.3.0'
  'typebox': 'catalog:'
  'undici@<6': '6.28.0'
  'update-notifier@>=4.0.0': '7.3.1'
  'uuid': '11.1.1'
  'which': '7.0.0'
  'wrap-ansi@>=8': '9.0.2'
  'yaml@2': '2.9.0'

  # Repo-specific overrides below.
  '@anthropic-ai/sdk': '0.91.1'
  # Dedup: @grpc/proto-loader 0.7 (dockerode) + 0.8 (@grpc/grpc-js) → 0.8.1.
  # Both CJS with a stable load/loadSync surface.
  '@grpc/proto-loader': '0.8.1'
  '@inquirer/ansi': '2.0.7'
  '@inquirer/core': '11.2.1'
  '@inquirer/figures': '2.0.7'
  '@npmcli/arborist': '9.9.0'
  '@npmcli/git': '6.0.3'
  '@npmcli/installed-package-contents': '4.0.0'
  '@npmcli/name-from-folder': '4.0.0'
  '@npmcli/promise-spawn': '9.0.1'
  '@npmcli/redact': '4.0.0'
  '@npmcli/run-script': '10.0.4'
  # Dedup: @polka/url 0.5 (polka) + 1.x (sirv) → 1.0.0-next.29 (dual CJS/ESM).
  # The paired patch re-adds @polka/url@0.5's callable default export that
  # polka@0.5.2 require()s.
  '@polka/url': '1.0.0-next.29'
  '@sigstore/core': '3.2.1'
  '@sigstore/sign': '4.1.1'
  '@types/unist': '3.0.3'
  'ajv-formats': '3.0.1'
  'ansi-regex': '6.2.2'
  # Dedup: ansi-styles 4 (CJS) + 6 (ESM-only) → 6.2.3. chalk@4 was the only
  # CJS require()r of the external ansi-styles; collapsing chalk up to 5 (which
  # vendors its own ansi-styles) leaves only ESM importers (wrap-ansi,
  # npm-run-all2), so no compat patch is needed here.
  'ansi-styles': '6.2.3'
  # Must match the `brace-expansion@>=4` override, the catalog pin, the soak
  # exclude and the patch key above — all four say 5.0.9. This bare key is more
  # specific, so at 5.0.8 it won and pinned resolution there, which orphaned
  # `patches/brace-expansion@5.0.9.patch` and made every install fail with
  # ERR_PNPM_UNUSED_PATCH.
  'brace-expansion': '5.0.9'
  # Dedup: chalk 4 (CJS; @yarnpkg/*, type-coverage) + chalk 5 (ESM-only;
  # ecc-agentshield) → 5.6.2. chalk 5 ships no `require` export condition, so a
  # CJS require() lands on the ESM namespace rather than the callable default;
  # the paired patch adds source/index.cjs restoring the chalk@4 require shape.
  'chalk': '5.6.2'
  'chownr': '3.0.0'
  # Dedup: commander 2/8/11/13 → 13.1.0. Only the CLI bins of terser/katex/svgo
  # reference commander (their library entry points don't); all four are CJS.
  'commander': '13.1.0'
  # Dedup: content-type 1 (express/body-parser) + 2 (type-is) → 2.0.0. Both
  # CJS; the paired patch restores content-type@1's req/res-object input that
  # body-parser@2.2.2 still calls parse() with.
  'content-type': '2.0.0'
  # Dedup: css-tree 2 (csso) + 3 (svgo) → 3.2.1. Both dual CJS/ESM.
  'css-tree': '3.2.1'
  'debug': '4.4.3'
  'diff': '9.0.0'
  'estraverse': '5.3.0'
  'fast-uri': '3.1.4'
  'globby': '16.2.2'
  'has-flag': '5.0.1'
  # 4.12.25+ clears GHSA-88fw-hqm2-52qc (hono CORS wildcard+credentials reflect),
  # pulled transitively via @anthropic-ai/claude-agent-sdk.
  'hono': '4.12.32'
  'hosted-git-info': '8.1.0'
  'ip-address': '10.3.1'
  'isexe': '3.1.5'
  # Dedup: js-tokens 4 (@babel/code-frame, CJS require) + 10 (ast-v8-to-istanbul,
  # ESM import) → 10.0.0. The two majors have incompatible APIs (v4 regex vs v10
  # generator); the paired patch serves js-tokens@4's regex+matchToToken on the
  # `require` condition and keeps the v10 generator on `import`.
  'js-tokens': '10.0.0'
  # 4.2.0 clears GHSA-h67p-54hq-rp68 (js-yaml quadratic merge-key DoS, <=4.1.1),
  # pulled transitively via @yarnpkg/core.
  'js-yaml': '4.3.0'
  'json-parse-even-better-errors': '5.0.0'
  'lru-cache': '11.5.2'
  'make-fetch-happen': '15.0.6'
  # Dedup: mimic-response 1 (clone-response) + 3 (decompress-response) → 3.1.0.
  # Both CJS with the same mimicResponse(from, to) surface.
  'mimic-response': '3.1.0'
  # Dedup: lifted from 9.0.9 to the newest line the fleet carries. 9's ESM
  # build ships named exports only, so the CI cache action's default import
  # throws "does not provide an export named 'default'" and kills the job at
  # setup before a check runs. 10 does not fix that on its own — it drops the
  # default too — so the paired patch restores it on BOTH builds, the same
  # treatment brace-expansion needs above.
  'minimatch': '10.2.6'
  'minipass': '7.1.3'
  'minipass-fetch': '4.0.1'
  'minipass-flush': '1.0.7'
  'minipass-sized': '1.0.3'
  'minipass@7': '7.1.3'
  'minizlib': '3.1.0'
  'npm-bundled': '5.0.0'
  'npm-normalize-package-bin': '5.0.0'
  'npm-package-arg': '12.0.2'
  'npm-pick-manifest': '10.0.0'
  'p-map': '7.0.6'
  'pacote': '21.5.1'
  'picomatch': '4.0.5'
  'postcss': '8.5.25'
  'proc-log': '6.1.0'
  'qs': '6.15.3'
  # Unify every rolldown resolution to the catalog pin (1.1.0). vite 8.0.14
  # bundles its own rolldown (1.0.2) transitively; without this override the
  # tree would carry two rolldown versions + two sets of platform bindings.
  'rolldown': 'catalog:'
  'semver': '7.8.5'
  'signal-exit': '4.1.0'
  'spdx-expression-parse': '4.0.0'
  'ssri': '12.0.0'
  'string-width': '8.2.2'
  'strip-ansi': '7.2.0'
  'supports-color': '10.2.2'
  # 7.5.16+ clears GHSA (node-tar PAX size-override parser differential, <=7.5.15).
  'tar': '7.5.22'
  # Dedup: tar-fs 2 (dockerode) + 3 (bundled into src/archives) → the catalog
  # pin, and its tar-stream 2/3 dep along with it → 3.2.0. Both are CJS;
  # dockerode is the only tar-fs@2 consumer (latent devtool).
  'tar-fs': 'catalog:'
  'tar-stream': '3.2.0'
  'terminal-link': '2.1.1'
  'tslib': '2.8.1'
  # Force EVERY transitive vite (via vitest, plugins) to the rolldown-native
  # 8.x catalog pin so esbuild never resolves into the tree.
  'vite': 'catalog:'
  'which@>=4': '7.0.0'
  'wrap-ansi': '9.0.2'
  'yaml': '2.9.0'
  # Dedup: yargs-parser 21 (yargs@17, CJS require) + 22 (bundled into
  # src/exe/argv/parse) → 21.1.1. 22 is ESM-only (no `require` export) and would
  # break yargs@17; 21.1.1 is dual CJS/ESM with the same parse surface and is
  # the version rolldown bundles for src.
  'yargs-parser': '21.1.1'
  'yoctocolors-cjs': '2.1.3'
  # Dedup: zod 3 (ecc-agentshield, dtu-github-actions) + 4 (claude-agent-sdk peer
  # ^4.0.0, mcp-sdk) → 4.1.12. claude-agent-sdk requires v4; the v3 consumers use
  # only the v4-compatible core surface (z.object/string/array/number/coerce/parse).
  'zod': '4.4.3'

patchedDependencies:
  # Published 6.7.0 requires two things it never declares: its own alias
  # `@socketsecurity/lib-stable/...` from five dist files, and bare `semver`
  # from dist/external/npm-pack.js in 13 places. Both resolved only on pnpm
  # hoisting and broke the moment a global virtual store took the hoist
  # directory off the resolution path. The patch points each at what the
  # package already ships. Remove it when the catalog pin moves to a release
  # carrying the source fixes.
  '@socketsecurity/lib@6.7.0': patches/@socketsecurity__lib@6.7.0.patch
  # Indirects the `node-gyp/bin/node-gyp.js` require.resolve so the rolldown
  # bundle doesn't statically inline node-gyp; consumer: pacote → run-script
  # in the bundled dist tree.
  '@npmcli/run-script@10.0.4': patches/@npmcli__run-script@10.0.4.patch
  # Dedup compat: re-adds @polka/url@0.5's callable default export (unparsed
  # `.query`) so polka@0.5.2 keeps working after the @polka/url 0.5/1 collapse.
  '@polka/url@1.0.0-next.29': patches/@polka__url@1.0.0-next.29.patch
  # Replaces the node:http2 constants import with inline lowercase header
  # literals so the browser bundle (which stubs http2 to false) can load the
  # sigstore signer; consumer: packages/provenance via the browser field.
  '@sigstore/sign@4.1.1': patches/@sigstore__sign@4.1.1.patch
  # Telemetry lockdown: removes TelemetryManager's Datadog ingest endpoint so
  # the dev-only @yarnpkg/core (reached via @yarnpkg/extensions, the
  # packageExtensions data pkg-ext/data.ts bundles) can never upload metrics;
  # the telemetry-deps-are-reviewed payload scan gates the shape.
  # On a bump, regenerate via `pnpm patch @yarnpkg/core` + `pnpm patch-commit`.
  '@yarnpkg/core@4.9.1': patches/@yarnpkg__core@4.9.1.patch
  # Dedup compat: adds a `require` export condition + source/index.cjs so the
  # ESM-only chalk@5 stays require()-able by chalk@4's CJS consumers (@yarnpkg,
  # type-coverage) after the chalk 4/5 collapse.
  chalk@5.6.2: patches/chalk@5.6.2.patch
  # Dedup compat: restores content-type@1's req/res-object input to parse() that
  # body-parser@2.2.2 still relies on, after the content-type 1/2 collapse.
  'content-type@2.0.0': patches/content-type@2.0.0.patch
  # Dedup compat: serves js-tokens@4's regex + matchToToken on the `require`
  # condition (for @babel/code-frame) while keeping js-tokens@10's generator on
  # `import`, after the js-tokens 4/10 collapse.
  js-tokens@10.0.0: patches/js-tokens@10.0.0.patch
  # default-export interop (managed by socket-wheelhouse sync; do not edit):
  # v10's ESM build ships named exports only, so `import minimatch from
  # 'minimatch'` throws "does not provide an export named default". That is
  # the shape `@actions/cache` resolves through, so an unpatched member dies
  # in the CI cache step at setup, before a single check runs. The patch adds
  # the default to BOTH builds; patching one leaves the other broken.
  # It also makes the `minimatch@>=3` hoist safe: a v3 consumer
  # (`@actions/glob@0.6.1` pulls 3.1.5) default-imports a callable, and the
  # patched v10 answers that same shape.
  # On a bump, regenerate via `pnpm patch minimatch` + `pnpm patch-commit`.
  minimatch@10.2.6: patches/minimatch@10.2.6.patch
  # minipass 7 ships a named export ({ Minipass }) where 3.x was a default;
  # these three re-pin the import shape + peer range so the deduped minipass 7
  # tree works; consumer: cacache/make-fetch-happen in src/external.
  minipass-flush@1.0.7: patches/minipass-flush@1.0.7.patch
  # Same minipass 7 named-export fix, plus buffer.length → bufferLength for
  # minipass 7's accessor rename; consumer: make-fetch-happen pipelines.
  minipass-pipeline@1.2.4: patches/minipass-pipeline@1.2.4.patch
  # Same minipass 7 named-export + peer-range fix; consumer: cacache writes.
  minipass-sized@1.0.3: patches/minipass-sized@1.0.3.patch
  # Drops the unused Find-VisualStudio.cs C# helper so the packed tree carries
  # no compiled-language source a scanner would flag; consumer: optional gyp
  # builds under allowBuilds.
  node-gyp@12.4.0: patches/node-gyp@12.4.0.patch
  # Swaps `instanceof Error` for the cross-realm Error.isError (with shim) so
  # cause chains survive vm/worker realms; consumer: errors/predicates parity
  # with src's own isError semantics.
  pony-cause@2.1.11: patches/pony-cause@2.1.11.patch
  # default-export interop (managed by socket-wheelhouse sync; do not edit):
  # 5.0.7 dropped the default export from BOTH builds. The CJS half breaks
  # minimatch@9's compiled `__importDefault`, which reads `.default` and
  # skips the namespace fallback once `__esModule` is set. The ESM half
  # breaks any `import x from 'brace-expansion'`, the shape the fleet CI
  # cache action resolves through, so an unpatched member throws "does not
  # provide an export named default" and dies at setup before a test runs.
  # The patch restores `expand` as the default on each build separately;
  # patching one build leaves the other broken.
  # On a bump, regenerate via `pnpm patch brace-expansion` + `pnpm patch-commit`.
  brace-expansion@5.0.9: patches/brace-expansion@5.0.9.patch
  # single-registry (managed by socket-wheelhouse sync; do not edit):
  # routes taze version resolution through its own bundled direct-registry
  # client (getVersionsFromRegistry — full packument, .npmrc/auth-aware) for
  # EVERY registry, instead of the fast-npm-meta hosted endpoint it uses
  # when the registry is the npm default. That third-party hop leaks
  # dependency names, violates the fleet single-registry posture, and is
  # blocked by egress policy — every lookup then hits the request timeout
  # while taze still exits 0 (false green; update.mts fails loud on it).
  # On a taze bump, regenerate via `pnpm patch taze` + `pnpm patch-commit`.
  taze@20.0.0: patches/taze@20.0.0.patch

# Opt out of pnpm's packageManager-version self-check. CI installs pnpm from
# its native bin via the shared setup workflow, not corepack, so the runner's
# pnpm legitimately differs from the `packageManager` pin (which is
# informational, not a version to enforce). Without this, pnpm hard-fails
# ("This project is configured to use <pin> ... your current pnpm is <run>")
# the moment the runner's pnpm differs from the pin.
managePackageManagerVersions: false

# pnpm 11's packageManager-version-check failure policy. `warn` lets the
# install proceed with a mismatched pnpm (emitting a warning) rather than
# hard-failing. `error` is the default when the field is absent — socket-lib
# had `error` while the wheelhouse lacked the field, which blocked commits
# under a dev pnpm that differed from the `packageManager` pin. `warn` keeps
# the pin informational without blocking CI or local dev.
pmOnFail: warn
trustPolicy: no-downgrade
trustPolicyExclude:
  - '@yarnpkg/core@4.5.0'
  - '@yarnpkg/libzip@3.2.2'
  - 'compromise@14.15.0'

# Auto-install missing peer deps (pnpm default). Declared explicitly
# so a future default flip can't silently change install behavior.
autoInstallPeers: true

# Never install esbuild. vite 8 declares it as an OPTIONAL peer
# (peerDependenciesMeta.esbuild) but the fleet bundler is rolldown, which vite
# 8 bundles natively — esbuild is dead weight here and only surfaces as noisy,
# non-reachable Dependabot advisories (the vuln is in esbuild's Deno module;
# this repo runs Node). Suppressing the optional dep keeps it out of the tree.
ignoredOptionalDependencies:
  - esbuild

# Pin pnpm's default of running root pre/post lifecycle scripts.
enablePrePostScripts: true

# Pin exact versions on `pnpm add`. Catalog and overrides should
# also be exact pins (5.24.0, not ^5.24.0).
saveExact: true