fix: resolve high and critical npm audit vulnerabilities - #23
Merged
Merged
Conversation
- Bump pinned next 16.2.12 -> 16.3.6 across templates/examples, fixing the critical unauthenticated RCE advisories (GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4). - Bump the sharp override 0.35.3 -> 0.35.4, fixing the high-severity libheif advisory (GHSA-rgj7-g3m4-5g8c) next@16.3.6 already wants but our override was pinning below. - fast-uri and js-yaml high-severity advisories cleared via npm audit fix. `npm audit --audit-level=high` now exits 0 (2 remaining moderate vitest/mocker findings require a vitest major bump, left alone). Verified lint, typecheck, test (99 passing), and build all still pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
next16.2.12 → 16.3.6 across templates/examples — fixes the two critical unauthenticated RCE advisories (GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4) that were blocking the release workflow'snpm audit --audit-level=highgate.sharpoverride 0.35.3 → 0.35.4 — fixes the high-severity libheif advisory (GHSA-rgj7-g3m4-5g8c).next@16.3.6already wantssharp@^0.35.4; our rootoverridesblock was pinning it below that.fast-uriandjs-yamlhigh-severity advisories cleared vianpm audit fix(no code changes, transitive-dep bumps only).npm audit --audit-level=highnow exits 0. Two moderatevitest/@vitest/mockerfindings remain — fixing those needs a vitest major bump (breaking), left alone since they're below the CI gate's threshold.Test plan
npm run lint— passesnpm run typecheck— passes across all workspacesnpm test— 99/99 passingnpm run build— succeeds (pre-existing content.ts tracing warnings only, unrelated)npm audit --audit-level=high— exit 0npm pack --dry-run --workspace packages/framework— tarball builds correctly at 0.5.0🤖 Generated with Claude Code