Repository navigation
security: pin postcss-selector-parser to 7.1.6 - #663
Merged
Merged
Conversation
cssnano's postcss-calc pulled a 6.x copy alongside the 7.x one the @csstools plugins use. Everything now resolves to the single patched release. The other two open alerts have no upstream fix: http-cache-semantics (via node-gyp, from fsevents and @parcel/watcher) and sprintf-js (via js-yaml 3 and argparse 1, from jest's coverage config loader) both report no patched version. Neither ships in the published packages. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Clears Dependabot #159 (medium, quadratic complexity in flat selector parsing).
cssnano's
postcss-calcpulled a 6.x copy ofpostcss-selector-parseralongside the 7.x one the@csstoolsplugins already use. Pinning the 6.x ranges collapses everything onto the single patched 7.1.6.yarn cipasses — the plugins that consume it run during stylelint and the postcss build step.The other two alerts have no fix
Both report no patched version upstream, so there's nothing to bump to:
http-cache-semanticsvianode-gyp←fsevents/@parcel/watchersprintf-jsviajs-yaml3 →argparse1 ← jest's@istanbuljs/load-nyc-configBoth are build/test-only transitives and neither is bundled into the published packages, which externalize only
dependenciesandpeerDependencies. Forcingjs-yamlto 4 would breakload-nyc-config, which calls thesafeLoadthat v4 removed. Suggest dismissing both until upstream patches land.🤖 Generated with Claude Code