Repository navigation
Conversation
postcss 8.5.6 is affected by four advisories, two of them high: - GHSA (arbitrary file read / info disclosure via attacker-controlled source map paths), patched in 8.5.12 - GHSA (path traversal in previous source map auto-loading), patched in 8.5.18 - two moderate advisories (XSS via unescaped </style>, incomplete fix of GHSA-6g55-p6wh-862q), patched in 8.5.10 and 8.5.23 8.5.30 is the current release and is above every patched floor. pnpm audit on this tree: 88 -> 81 findings, postcss advisories 4 -> 0. postcss is a devDependency (build-time only), so there is no runtime change; lockfile diff is limited to postcss and its transitive deps.
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
postcss8.5.6 → 8.5.30 inpackage.json(+ lockfile).Why
pnpm auditreports four advisories againstpostcss@8.5.6, two of them high severity. All four floors are cleared by 8.5.30:<=8.5.11<=8.5.17<8.5.10</style>in CSS stringify output<=8.5.22map.contentpostcsshere is the one behindautoprefixer/tailwindcss, i.e. build-time only, so this is not a runtime exposure on its own — but it is the only direct dependency in this repo with open high-severity advisories, and everything else flagged by audit is transitive throughnextra/mermaid/katexand needs upstream releases.Verification
pnpm audit: 88 → 81 findings (54 → 49 high, 28 → 26 moderate);postcssadvisories 4 → 0pnpm run lint:js,pnpm run lint:mdx,pnpm run buildon the patched tree: all exit 0postcssand its transitive deps (nanoiddrops out entirely,source-map-jsmoves to 1.2.2)pnpm --versionmatches the repo'spackageManagerfield (pnpm@9.12.3), so the lockfile format is unchangedNo other package is touched;
autoprefixer/tailwindcss/nextare left alone to keep the diff reviewable.