You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracks the v2.5.0 milestone release: the audit, the version PRs (Version Packages, Prepare Python Release), the v2/main → main merge PR, the release ledger, and the Release. Closed by hand once the Release is published.
Every Python server was audited (verdict present for each).
The picomatch finding: no fix available, and not reachable from a server
No patched release exists. The advisory's range is <= 4.0.7 with no first patched version, and 4.0.7 is the registry's latest. The lockfile resolves picomatch@4.0.7 (six copies) and 2.3.2 (one, under micromatch). The only "fix" npm offers is npm audit fix --force, which downgrades vitest to 3.1.4; that is ruled out (AGENTS.mdDependencies).
It is in development tooling only.npm ls picomatch --omit=dev is empty: it arrives through vitest/vite/tinyglobby, typescript-eslint, @changesets/cli and shx. No published package depends on it, so nothing this release publishes carries it. The globs those tools match are the repository's own.
Outcome: nothing to change. No fixes were forced, so there is no audit PR. No tracking issue for the advisory exists yet; the daily alert sweep is the one that files a no-patched-release advisory for a decision.
Activity
cliffhall commentedon Nov 18, 2026
Release audit (step 2a)
Audited at
origin/v2/main4b6f0954.npm audit --audit-level=highpicomatchGHSA-fc5q-39xc-vjpf (ReDoS through single-branch repeated extglobs) and the packages that depend on itnpm audit --omit=devmcp-server-fetchlocked requirements,pip-audit --require-hashesmcp-server-gitlocked requirementsmcp-server-timelocked requirementsEvery Python server was audited (verdict present for each).
The
picomatchfinding: no fix available, and not reachable from a server<= 4.0.7with no first patched version, and4.0.7is the registry'slatest. The lockfile resolvespicomatch@4.0.7(six copies) and2.3.2(one, undermicromatch). The only "fix" npm offers isnpm audit fix --force, which downgradesvitestto 3.1.4; that is ruled out (AGENTS.mdDependencies).npm ls picomatch --omit=devis empty: it arrives throughvitest/vite/tinyglobby,typescript-eslint,@changesets/cliandshx. No published package depends on it, so nothing this release publishes carries it. The globs those tools match are the repository's own.Outcome: nothing to change. No fixes were forced, so there is no audit PR. No tracking issue for the advisory exists yet; the daily alert sweep is the one that files a no-patched-release advisory for a decision.