Clear the two advisories that turned the audit gate red - #181
Merged
Merged
Conversation
Merging #177 took the critical Next.js pair and the four fast-uri advisories off the board, and two published since took their place, so the gate stayed red on main and on every open PR — it runs per-PR, which is why a documentation-only branch also shows it failing. Both fixes are patch-level: - sharp <0.35.4 (GHSA-rgj7-g3m4-5g8c, libheif) — the devDependency and the existing override both moved to ^0.35.4. next 15.5.25 wants that version anyway: it re-enables AVIF image optimization only when a sharp new enough to carry the libheif fix is installed. - js-yaml >=4.0.0 <4.3.2 (GHSA-2883-xcg3-v3hh, maxTotalMergeKeys does not limit CPU on empty merge sources) — dev-only, reached through eslint 8.57.0, which pins the vulnerable range. An override to ^4.3.2 is a patch bump inside the same major, so eslint keeps the API it expects. Lockfile refreshed with --package-lock-only. `node scripts/audit-gate.js --level=high` now passes with one active exception, the dated deepmerge-ts one that expires 30/09. Co-Authored-By: Claude Opus 5 <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.
Merging #177 took the critical Next.js RCE pair and the four
fast-uriadvisories off the board, and two advisories published since took their place. The gate is red onmainand therefore on every open PR — it runs per-PR, which is why the documentation-only #179 also showsnpm audit + SBOMfailing.Both fixes are patch-level:
sharp <0.35.4^0.35.4maxTotalMergeKeysdoes not limit CPU on empty merge sources)js-yaml >=4.0.0 <4.3.2eslint@8.57.0^4.3.2next15.5.25 wants the newersharpanyway: it re-enables AVIF image optimization only when asharpnew enough to carry the libheif fix is installed. Thejs-yamloverride stays inside the same major, so eslint keeps the API it expects.Lockfile refreshed with
npm install --package-lock-only. Locallynode scripts/audit-gate.js --level=highnow passes, with one active exception: the dateddeepmerge-tsone that expires 30/09.🤖 Generated with Claude Code