security: close the postcss HIGH advisory in memory-router#67
Merged
Conversation
CVE sweep, 2026-07-25. This repo was missed in the main sweep pass: it has no root package.json, so a repo-level `npm audit` reads nothing. Closed: postcss <=8.5.17, GHSA-r28c-9q8g-f849, in packages/memory-router. The other two packages were already clean. Lockfile-only, no package.json change, no override, within-major. Verification: npm audit 0 critical / 0 high in all three packages; `npm install --package-lock-only` a no-op in each, proving lockfile coherence; typecheck, lint, test and build pass in all three. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
LanNguyenSi
added
review:tests-pass
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.
Closes
postcss <=8.5.17(GHSA-r28c-9q8g-f849) inpackages/memory-router. The other two packages were already clean.Lockfile-only per package. No
package.jsonchange, no override, all bumps within-major per the sweep procedure.This repo was missed in the main sweep pass — it has no root
package.json, so a repo-levelnpm auditreads nothing. Found by re-checking every repo without a root manifest after the operator spotted the same gap in agent-dx.Verification
npm audit0 critical in every packagenpm install --package-lock-onlyis a no-op in each, proving lockfile coherence