Repository navigation
Conversation
…GHSA-rj75-hqrm-r3gf) Dev-only transitive dependency (via tailwindcss, postcss-nested), fixed with a package.json override since both parents already allow >=6.1.5 in their own semver ranges — no parent release needed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V7BdiatmGjPa7HdVN4oDgn
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.
Weekly dev-only CVE batch (Zero-CVE routine, Monday run).
Advisory closed: GHSA-rj75-hqrm-r3gf — PostCSS: quadratic complexity in flat selector parsing allows CPU exhaustion (moderate, CVSS 5.9).
Package changed:
postcss-selector-parser6.1.4 → 6.1.5 (patch, dev-only transitive dependency pulled in bytailwindcssandpostcss-nested).Risk class: patch — no code changes, package bump only.
Both parents already declare semver ranges (
^6.1.2,^6.1.1) that permit 6.1.5, so no parent release was needed; added apackage.jsonoverridesentry to force the resolution and regenerated the lockfile. Verified withnpx tsx scripts/check-lockfile-registry.tsthat every package still resolves from the public npm registry only.Test evidence:
npm ci --ignore-scripts && npm rebuild better-sqlite3 esbuild unrs-resolver— cleannpx tsx scripts/check-lockfile-registry.ts— all packages resolve from the public registrynpm test— 261 suites / 3540 tests passednpx tsc --noEmit— no errorsnpm run build— succeedednpm run test:smoke(Playwright) — 6/6 passedTracked under the Zero-CVE routine; this is dev-only (not in the
--omit=devaudit), no runtime impact.Generated by Claude Code