chore(deps): bump postcss to 8.5.23 to close path-traversal advisory - #2215
Merged
Conversation
The committed site/pnpm-lock.yaml pinned postcss 8.5.15 (via astro > vite), which is affected by GHSA-r28c-9q8g-f849 (high: path traversal in previous source map). vite's transitive range keeps it below the 8.5.18 patch, so add a pnpm override forcing postcss >=8.5.18; it resolves to 8.5.23. nanoid moves 3.3.12 -> 3.3.16 as postcss's own transitive dep. pnpm audit for site is now clean; frozen-lockfile install verified. Note: the brace-expansion high advisory (GHSA-mh99-v99m-4gvg) surfaced by pnpm audit is a false positive here - the installed 2.1.2 already carries the bounded-expansion DoS fix (the advisory range only credits 5.0.8), and forcing 5.x breaks minimatch's require() interop, so no change is made there.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 52085bb | Commit Preview URL Branch Preview URL |
Jul 27 2026, 09:34 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Pins
postcssto8.5.23in thesite/project via apnpm.overridesentry, closing the open high-severity Dependabot alert on the default branch (path traversal in the previous source map). No site behavior changes — postcss is a build/transform dependency and this is a patch-level bump within8.5.x.Why
site/pnpm-lock.yamlresolvedpostcss@8.5.15transitively (astro > vite > postcss), which is affected by GHSA-r28c-9q8g-f849 (high: PostCSS path traversal in previous source map, vulnerable<= 8.5.17). vite's transitive range keeps postcss below the8.5.18patch, so apnpmoverride is required — matching the existing security-override pattern already insite/package.json(esbuild,undici,ws,yaml, …).nanoidmoves3.3.12 → 3.3.16as postcss's own transitive dependency; no other resolutions change.Before / After
Note on the other
pnpm auditfindingpnpm auditalso reports a high forbrace-expansionundercrates/bashkit-js(dev/test tooling,ava > @vercel/nft > glob > minimatch). That one is not actionable and is intentionally left unchanged:brace-expansion@2.1.2already contains the bounded-expansion DoS fix (itsexpand()ismax-bounded; the vulnerable2.0.1is not). The advisory's OSV range only credits5.0.8, which is why the scanner still flags it.5.xbreaksminimatch@9'srequire('brace-expansion').default(...)interop (verified locally —TypeError: … .default is not a function), so a major override would break the test toolchain for no security benefit.Risk
8.5.15 → 8.5.23is a patch-level bump on a build dependency; the site build is exercised bysite.ymlon this PR. No runtime/shipped-code change.Checklist
site.ymlbuild +pnpm auditcover it)Generated by Claude Code