weekly-fixes/2026-06-21: patch brace-expansion & js-yaml DoS advisories#13
Open
gndclouds wants to merge 1 commit into
Open
weekly-fixes/2026-06-21: patch brace-expansion & js-yaml DoS advisories#13gndclouds wants to merge 1 commit into
gndclouds wants to merge 1 commit into
Conversation
Lockfile-only bumps resolved by `npm audit fix --package-lock-only` — no package.json semver ranges changed, all drop-in non-breaking updates: - brace-expansion 5.0.5 -> 5.0.6, 1.1.12 -> 1.1.15 (GHSA-f886-m6hf-6m8v zero-step sequence hang/OOM, GHSA-jxxr-4gwj-5jf2 large numeric range defeats max DoS guard) - js-yaml 4.1.1 -> 4.2.0 (GHSA-h67p-54hq-rp68 quadratic merge-key alias DoS) Both are dev-tooling transitives. yarn.lock left untouched: npm rewrites it destructively (drops platform sharp/emnapi binaries), so the dual-lockfile item stays for human review as flagged in #12. Verified: npm ci, npx tsc --noEmit, npx eslint . all clean. No test suite. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 maintenance — 2026-06-21
Automated weekly review of the most recent PR(s) + dependency/security audit. This run found one concrete, safely-fixable item (two moderate DoS advisories in dev-tooling transitives) and fixes it here. Everything else ran clean or is an existing human-review item.
What changed (security/packages)
Lockfile-only bumps via
npm audit fix --package-lock-only— nopackage.jsonsemver ranges changed, all drop-in non-breaking updates:brace-expansionmaxDoS guard)js-yamlBoth are dev-tooling transitives (eslint/glob, config loaders). DoS-only, not on a production request path, but cheap and safe to patch.
Verification
npm ci— installs clean against the updated lockfilenpx tsc --noEmit— cleannpx eslint .— cleanThe four checks, in full
ai-site-theme.tsdefault-model bump toclaude-sonnet-4-6). The model bump is correct —claude-sonnet-4-6is a current, valid model id and theANTHROPIC_MODELoverride path is unchanged. No correctness regressions found.package.jsonranges are healthy; this PR only patches the two transitive advisories above inpackage-lock.json. Dual-lockfile situation persists (see "Needs human review").npm auditnow reports 2 moderate remaining, both the nestedpostcss(<8.5.10,</style>stringify XSS) bundled insidenext. Fixing it requiresnpm audit fix --force(Next.js major downgrade), which is unsafe — left for a deliberate upgrade. No committed secrets, injection, or unsafe deserialization introduced by recent changes.Needs human review (not fixed here)
postcssXSS insidenext. Only fixable by changing thenextmajor version — out of scope for a minimal lockfile patch.package-lock.jsonandyarn.lockare committed. Runningnpm audit fixrewritesyarn.lockdestructively (drops platform-specific@img/sharp-*and@emnapi/*binaries), so I deliberately leftyarn.lockuntouched and updatedpackage-lock.jsononly — same convention as weekly-fixes/2026-06-19: patch critical/high dependency advisories (handlebars, next, postcss, defu, effect) #12. Recommend standardizing on npm and removingyarn.lock; it's a maintainer decision tied to the Vercel build config.@anthropic-ai/sdksits at^0.105.0(current). No action needed this run.Context
Follows the previous weekly run #12, which patched the critical/high advisories (handlebars, next, defu, effect). Branched off
main; original branches untouched; one PR this run.🤖 Generated with Claude Code