Skip to content

deps: bump picomatch to 2.3.2 and 4.0.4 in package-lock.json - #157

Closed
katsugtgz wants to merge 1 commit into
Valian:mainfrom
katsugtgz:deps-picomatch-lockfile
Closed

katsugtgz wants to merge 1 commit into
Valian:mainfrom
katsugtgz:deps-picomatch-lockfile

Conversation

@katsugtgz

Copy link
Copy Markdown
Contributor

Updates picomatch to 2.3.2 and 4.0.4 in package-lock.json to address GHSA-c2c7-rcm5-vvqj and GHSA-3v7f-55p6-f55p.

Evidence:

  • package-lock.json resolved picomatch@2.3.1 (under anymatch, micromatch, readdirp) and picomatch@4.0.3 (root)
  • OSV reports GHSA-c2c7-rcm5-vvqj and GHSA-3v7f-55p6-f55p against those versions
  • updated versions: picomatch 2.3.2 and picomatch 4.0.4, both clear of all current advisories per OSV

Validation:

  • npm ci succeeds with the updated lockfile
  • osv-scanner no longer reports picomatch

Note: this patch is lockfile-only. The package.json ranges (^2.0.4, ^4.0.2, ^4.0.3) already cover the new versions, so a separate manifest change is not required.

Scope: package-lock.json only, four picomatch entries; no other packages touched.

@katsugtgz katsugtgz closed this Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant